<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
	<!-- $Id: help.html 1500 2011-03-01 19:32:53Z ftruscot $ -->

	<title>Nucleus Admin Help</title>
	<style type="text/css">
	<!--
		body {
			font-family: verdana, arial;
			font-size: small;
		}

		h1 {
			font-size: large;
			border-bottom: 1px gray dashed;
			color: #596d9d;
			text-align: left;
		}

		h2 {
			font-size: medium;
			border: 1px solid #ddd;
			background-color: whitesmoke;
			text-align: left;
		}

		.page {
			height: 2400px;
			text-align: justify;
			margin-bottom: 100px;
		}

		pre {
			background-color: #ddd;
			padding: 5px;
			font-size: small;
		}

		.example {
			background-color: #ddd;
			padding: 5px;
		}

		ul.templates {
			font-size: x-small;
			line-height: 1.1;
			list-style: none;
			text-indent: -20px;
			margin-left: 20px;
		}

		ul {
			text-align: left;
		}

		a:link, a:visited {
			color: #1D3565;
			font-weight: bold;
			text-decoration: underline;
		}

		a:hover {
			background-color: whitesmoke;
		}

		.deprecated {
			border: 3px solid red;
			padding: 5px;
			font-size: medium;
		}

		tt, code {
			font-size: small;
		}

		table {
			border: 1px solid #ccc;
		}

		th {
			background-color: #eee;
		}

		td {
			vertical-align: top;
		}

		.note {
			background-color: #eee;
			padding: 5px;
		}
	-->
	</style>
</head>
<body>

<div class="page">
<h1>Nucleus Popup Help</h1>
<p>Please hold on while the page is being downloaded (about 100KB).</p>
</div>


<div class="page">
<a name="future"></a>
<a name="allowpastposting"></a>
<h1>Add Later/Earlier</h1>
<h2>Add Later</h2>
<p>The 'Add Later' option on add-item forms allows you to mark an item to become visible only at the exact time you've specified. Before that time has come, the item will not be viewable anywhere in the public part of your site.</p>
<p>This date <strong>must</strong> be in the future, unless the 'Allow posting to the past' option is enabled for the blog to which you want to add the item.</p>
<h2>Allow posting to the past</h2>
<p>When enabled, you'll be allowed to specify the date on which an item should be added, and to edit the timestamp of already existing items.</p>
</div>

<div class="page"><a name="changedate"></a>
<h1>Change post date/time</h1>
<p>
The 'Update Timestamp' option allows you to change the posting date and/or time of an item. If you changed the content of an item, this is a way bring the story back to the top of your front page.</p>
<p>But, the unique id connected to the item will not change, so your visitors can still find out that the item was originally posted later than items with a lower id.</p>
</div>


<div class="page"><a name="autosave"></a>
<h1>Autosave</h1>
<p>The Autosave function saves an item as a <a href="#draft">draft</a> after 10 minutes editing. It should avoid that unsaved changes get lost. It is usefull for users that work for a long time on an item and often forget to save their work.</p>
<p>If you want to invoke Autosave before the 10 minutes are past, you can press the '<strong>Auto save now</strong>' button at the end of the form.</p>
<p>The Autosave function can be enabled and disabled in the member options.</p>
</div>


<div class="page"><a name="draft"></a>
<h1>Drafts</h1>
<p>
Draft items are not yet viewable in the public blog. They might come in handy when you are working on a story, and something comes in between. Your draft items will be listed on the main page, so you can continue your work when you have the time to do so.</p>
<p>When editing drafts, choose the '<strong>Add now</strong>' radiobutton and hit the 'Edit item' button to make them visible.
</p>
</div>

<div class="page"><a name="extended"></a>
<h1>Extended part</h1>
<p>
Items have an optional extended part that you can use for continued stories. e.g. when a story is too long to put on the main page of your blog, you can write an introduction in the body part and the rest in the extended part. When viewing your main blog page, you will then see 'read more' links (as defined by the templates).
</p>
<p>
If you want to write an introduction only for <em>some</em> of your items, you could use the <a href="#templatevar-smartbody">smartbody</a> template variable to make a selection out of the body text and the extended text.
</p>
</div>

<div class="page"><a name="shortblogname"></a>
<h1>Short Blog Name</h1>
<p>
The short blog name is used mainly in the admin area to indicate which items are associated with which blog.
</p>
<p>
It can also be used in alternative index files, to make a second weblog available:
</p>
<pre>
&lt;?
	include('./config.php');
	selectBlog('myshortblogname');
	selector();
?&gt;
</pre>
</div>

<div class="page"><a name="blogdefaultskin"></a>
<h1>Default Skin</h1>
<p>
The default skin selected in the blog settings is the skin that should be used when the blog is displayed, and there is no other skin selected (through arguments in the URL)
</p>
</div>


<div class="page"><a name="blognotify"></a>
<h1>Notify Address</h1>
<p>
This option contains one or multiple e-mail addresses to which notification e-mails should be sent when new comments are added. Leave empty if you don't want notification. The given e-mail addresses must, of course, be valid.
</p>
<p>
If you're using multiple addresses, you should use a semicolon (<strong>;</strong>) as a separator.
</p>
<div class="note">
<b>Note:</b> As the maximum length of the settings fields is 128 characters, there's only a limited amount of e-mail addresses you can list.
</div>
<div class="note">
<b>Note:</b> When you set up your own e-mail address as notification address, you won't get notified of the items/comments that you wrote yourself. Assuming that you know what you wrote, that shouldn't be a problem.
</div>
</div>

<div class="page"><a name="blogmaxcomments"></a>
<h1>Max Amount of Comments</h1>
<p>
This is the maximum number of comments that will be shown on the <em>main page</em>. <strong>This is NOT a restriction on the total number of comments that can be made</strong>. On the detail pages, all comments will be shown, even if there are more than the maximum amount chosen.
</p>
<p class="note"><strong>Note:</strong>
Inside templates, this variable can be overridden by an optional parameter of the <a href="#templatevar-comments">comments</a> templatevar.
</p>
</div>

<div class="page"><a name="blogtimeoffset"></a>
<h1>Time Offset</h1>
<p>
If the time on your server is not equal to the time where you live, you might want to add an offset to the server time in order to get the correct time. Use negative values to subtract (negation sign). The current server time is listed as a reference.
</p>
<h2>Example</h2>
<p>If your local time is 20:35 and the server time is listed as 14:35, you'll need to set the time offset equal to 6 in order to get your blog time to 20:35
</p>
<p class="note"><strong>Note:</strong> Fractional offsets can be used as well, for people living in half time zones. e.g. an offset of <strong>1.5</strong> equals an offset of 1 hour and 30 minutes.</p>
</div>

<div class="page"><a name="blogupdatefile"></a>
<h1>Update File</h1>
<p>
Nucleus can edit a file for you whenever a new item is added to the blog. The contents of that file will be a timestamp of the last change. The use of such a file could be useful for services which check a file on your server once in a while to see if there were updates, and generate 'updated weblogs' from that. Pointing them to your main blog could cause false update warnings to be sent out when visitors add comments or when you change something to the skins or templates.
</p>
<p>
When you don't need an update file, just leave the field empty.
</p>
<p>
Please note that the location of the update file is relative to the admin-area, so you might want to use an absolute path (something like <tt>/path/to/your/website/update.txt</tt>). Also make sure the update file already exists and is writable (<a href="tips.html#filepermissions" onclick="window.open(this.href);return false;" class="out" title="quick guide on changing file permissions">chmod it to 666</a> if you want to be sure).
</p>
</div>

<div class="page"><a name="teamadmin"></a>
<h1>Blog Admin</h1>
<p>
Blog administrators have the following extra rights:
</p>

<ul>
	<li>They can manage the team</li>
	<li>They can edit blog settings</li>
	<li>They can edit/delete all items by all authors (from the blog of which they are admin)</li>
	<li>They can delete the blog</li>
</ul>

<p>
A blog can have multiple admins, but there must be at least one admin at all times.
</p>
</div>


<div class="page"><a name="superadmin"></a>
<h1>Administrator Privileges</h1>

<p>
A so called <em>super-admin</em> has <strong>full access</strong> to all functions and all weblogs, even if she is not on the blog team.
</p>

<p>
On top of that: a super-admin has the right to create new weblogs, to change general settings, to change templates, to change skins and to manage the members (creation/ manipulation/ deletion of members).
</p>

<p>
Usually, there will be only one super-admin, the site administrator.
</p>

</div>

<div class="page"><a name="canlogin"></a>
<h1>Can Login?</h1>
<p>
As a <a href="#superadmin" title="Administrator Privileges">superadmin</a>, you can disallow individual members to login to the admin area.
</p>
</div>

<div class="page"><a name="defaultblog"></a>
<h1>Default Blog</h1>
<p>
This is the blog that will be used when no other blog has been specified in the request.
</p>
</div>

<div class="page"><a name="baseskin"></a>
<h1>Base Skin</h1>

<p>The option tells Nucleus which skin to fall back to when no such decision can be automatically made. This happens when skin parts are empty, when no blog or skin is implicitly/explicitly selected.</p>
<p>Most users don't need to worry about this setting.</p>
</div>

<div class="page"><a name="cookies"></a>
<h1>Cookies</h1>

<h2>Cookie Lifetime</h2>
<p>
When a member logs in, a cookie is stored in his browser, so she doesn't need to log in again when she comes back the next day. The lifetime of this cookie decided when it will become invalid:</p>
<ul>
	<li><strong>Session cookies</strong> get deleted when you exit the browser</li>
	<li>Cookies with a lifetime of <strong>one month</strong> will stay on the computer until you don't use/visit the site for a month. Using this option, you'll never have to login again (unless you've logged out yourself, or logged in from another computer)</li>
</ul>

<h2>Cookie Path &amp; Cookie Domain</h2>
<p>
These settings are advanced settings. Normally, you shouldn't change them at all. In that case, cookie path is a simple slash ('/') and cookie domain is empty.
</p>

<h2>Secure Cookies</h2>
<p>
Normally, this should be set to 'no'. You should only set it to 'yes' when you have a HTTPS url and want cookies only to be sent over such a https connection.
</p>

<h2>'Last Visit' Cookie</h2>
<p>
You can setup Nucleus to store a cookie in which the time of the visitors last visit is stored. This can be used to put indications next to <a href="#templatenew">new items</a>
</p>

</div>


<div class="page"><a name="language"></a>
<h1>Language</h1>
<p>
You can choose a language to be used when nucleus creates content for you. The content generated by Nucleus includes the admin-area, the error messages, forms in skins, ...
</p>

<p>
There are two places where a language can be chosen: the global site settings include a language option.
Next to that, logged in members can override this setting if they want to.
</p>

<p>
When both of these settings are invalid, 'english' is used as the default language.
</p>

<p class="note"><strong>Note:</strong> Extra language files can be downloaded from the <a href="http://www.nucleuscms.org/" onclick="window.open(this.href);return false;" class="out" title="Nucleus CMS Website">Nucleus Website</a>. (opens a new window)</p>

</div>

<div class="page"><a name="allowaccountcreation"></a>
<h1>Account Creation</h1>
<p>
You can either allow or disallow your visitors to create their own 'member' account. They won't be allowed to add items to a blog (unless the admin adds them to a team), but they can login to the administration area and change their settings, and even delete or modify the comments they made.
</p>
</div>

<div class="page"><a name="allownewmemberlogin"></a>
<h1>New Member: can login ?</h1>
<p>
When you allow <a href="#allowaccountcreation">creation of member accounts</a> by your visitors, this setting defines whether or not accounts created in that way will have the ability to <a href="#canlogin">login to the administration area</a>.
</p>
</div>


<div class="page"><a name="messageservice"></a>
<h1>Message Service</h1>

<p>
For the privacy of your members, you can hide all e-mail addresses and allow members to send an e-mail message to each other through the script. The message that will be sent out will however contain the e-mail addresses of both users, so they can then do continued communication through regular e-mail. This service can be disabled.
</p>

<h2>Non-members</h2>
<p>
By default, non members cannot use the message service (because there's no way to check the validity of the e-mail address they enter). You can relax this restriction by allowing non-members to use the message service too. When submitting a message, they will be asked to enter their e-mail address, which will show up in the <tt>From:</tt> headers of the e-mail you receive.
</p>

</div>

<div class="page"><a name="disablesite"></a>
<h1>Disable Site</h1>
<p>
It's possible to disable your entire Nucleus site. You might want to do this when you are doing some configuration, or when something went horribly wrong :-)
</p>
<p>
The URL that needs to be configured is an URL to which the visitor will be redirected.
</p>
<p>
Exceptions: the <strong>admin-area</strong> is still available, and <strong><a href="#superadmin">super-admins</a></strong> can still see the entire site. (don't forget to re-enable your site afterwards ;-))
</p>
</div>


<div class="page"><a name="urlmode"></a>
<h1>URL Mode</h1>
<p>Using this option, you can switch between URL styles:</p>
<ul>
	<li><strong>Normal</strong>: URLs looking like <code>http://host/index.php?itemid=1234</code></li>
	<li><strong>Fancy</strong>: URLs looking like <code>http://host/item/1234</code></li>
</ul>
<p class="note"><strong>Note:</strong> In order to get the 'Fancy URL' mode working, some extra actions are required. They're described in the <a href="tips.html" class="out" onclick="window.open(this.href);return false;">Tips &amp; Suggestions</a> (opens in new window)</p>

</div>

<div class="page"><a name="defaultlistsize"></a>
<h1>Default List Size</h1>
<p>(3.40) Using this option, you can set the default size of lists in the Admin Area. Value should be an integer. 10 is a good default for most users.</p>
</div>

<div class="page"><a name="debugvars"></a>
<h1>Debug Vars</h1>
<p>(3.40) Using this option, you can set whether unresolved Vars (SkinVars, TemplateVars, ItemVars) are shown on the blog. Default is <code>No</code>.</p>
</div>

<div class="page"><a name="templateitems"></a>
<h1>Templates: Items</h1>
<p>
When items are shown, the following setup is repeated for each item:
</p>

<pre>
item header
item body
item footer
</pre>

<p>These three blocks all refer to a template-part, which define what the result looks like.</p>

<h2>Variables</h2>

<p>Within these template, a series of so called <a href="#templatevars-overview" title="Find out which variables are available">template variables can be used</a> to insert item data.</p>

<h2>Example</h2>
<p><a href="#templateitemsexample">An example</a></p>

</div>

<div class="page"><a name="templateitemsexample"></a>
<h1>Templates: Items</h1>
<p>
An example for the <b>item body</b> template:
</p>

<pre>&lt;h1&gt;&lt;%title%&gt;&lt;/h1&gt;

&lt;p&gt;&lt;%body%&gt;&lt;/p&gt;

&lt;div class="metadata"&gt;
 &lt;a href="&lt;%itemlink%&gt;"&gt;link&lt;/a&gt; -
 &lt;%date%&gt; &lt;%time%&gt; -
 &lt;a href="&lt;%authorlink%&gt;"&gt;&lt;%author%&gt;&lt;/a&gt; -
 &lt;%comments%&gt;
&lt;/div&gt;</pre>

<p>The result would become something like this:</p>

<div class="example">
<h4 style="margin: 2px;">This is an item</h4>
<p style="margin: 2px; padding: 0px;">This is the text for the item</p>
<div style="font-style: italic; margin: 2px;">
 <a href="#templateitemsexample">link</a> -
 August 8th 2002 18:51 -
 <a href="#templateitemsexample">karma</a> -
 <a href="#templateitemsexample">no comments</a>
</div>
</div>

</div>


<div class="page"><a name="templatecomments"></a>
<h1>Templates: comments</h1>

<p>There are three possible structures for a comments block.</p>

<ol>
	<li>
		When comments are displayed (like on detail pages, or on the main page when there are less than the maximum allowed amount of comments)
<pre>comments header
  comments body (repeated)
comments footer</pre>
	</li>
	<li>
		When there are no comments at all
<pre>
no comments
</pre>
	</li>
	<li>
		When there are comments, but there are more than the maximum allowed number. (only applies when not on a detailed item page)
<pre>
too much comments
</pre>
	</li>
</ol>

<p>Inside these template-parts, some <a href="#templatevars-comments" title="Overview of comments-related template variables">comments-related variables</a> are available</p>

</div>

<div class="page">
<a name="templatecommentheaders"></a>
<a name="templatecommentfooters"></a>
<h1>Templates: Comment headers/footers</h1>

<h2>Description</h2>

<p>While the comments-body is repeated for each comment, the header and footer are only displayed once. A typicall structure would look like this:</p>
<pre>comments header
  comments body 1
  comments body 2
  comments body 3
comments footer</pre>
<p>In these template-parts, <a href="#templatevars-comments" title="Overview of comments-related template variables">comments-related templatevars</a> are available</p>

<h2>Examples</h2>

<p>Header:</p>
<pre>&lt;ul&gt;</pre>
<p>Body:</p>
<pre>&lt;li&gt;&lt;%user%&gt;: &lt;%body%&gt;&lt;/li&gt;</pre>
<p>Footer</p>
<pre>&lt;/ul&gt;</pre>
<p>Result</p>

<ul class="example">
	<li>karma: nice!</li>
	<li>xiffy: yes indeed!</li>
</ul>

</div>

<div class="page"><a name="templatemorelink"></a>
<h1>Templates: Link to extended entry</h1>
<p>
This is the template that will be used to format the <a href="#templatevar-morelink">morelink templatevar</a> that is available in the item templates. <a href="#templatevars-overview">Available variables</a> are the same as in the item templates.
</p>
<p>
When there's no extended part of the item, the <code>&lt;%morelink%&gt;</code> templatevar will have no effect.
</p>

<h2>Example</h2>
<pre><code>&lt;a href="&lt;%itemlink%&gt;"&gt;[Read More!]&lt;/a&gt;</code></pre>

</div>

<div class="page"><a name="templatearchivelists"></a>

<h1>Templates: Archive Lists</h1>

<p>The archive lists are formatted as listed below:</p>

<pre>archivelist header
  archivelist listitem (repeated for each archive)
archivelist footer</pre>

<p>
Available variables: (in the header and footer, only <tt>blogid</tt> is allowed)
</p>

<table><tr>
	<th>Name</th>
	<th>Description</th>
</tr><tr>
	<td>blogid</td>
	<td>ID of the weblog</td>
</tr><tr>
	<td>archivelink</td>
	<td>link to the archive, which you can embed in a <code>&lt;a href=".."&gt;</code> tag.</td>
</tr><tr>
	<td>month</td>
	<td>Number of the month (2 digits: 01-12)</td>
</tr><tr>
	<td>year</td>
	<td>Year (4 digits)</td>
</tr><tr>
	<td>day</td>
	<td>Day of month (2 digits; only when in day mode)</td>
</tr></table>

<p>A more flexible way to add the date of the archive to the listitem, is to use <a href="#strftime">strftime</a> variables. If you find this too complicated, use the following:</p>

<pre><code>&lt;a href="&lt;%archivelink%&gt;"&gt;%B, %Y&lt;/a&gt;&lt;br /&gt;</code></pre>


<p>To change the language to your local settings, change the <a href="#templatelocale">locale</a>.</p>

</div>




<div class="page"><a name="templatecategorylists"></a>
<h1>Templates: Category Lists</h1>

<p>The category lists are formatted as listed below:</p>

<pre>categorylist header
  categorylist listitem (repeated)
categorylist footer</pre>

<p>Available variables: (in the header and footer, only <tt>blogid</tt>, <tt>blogurl</tt>, <tt>self</tt>, <tt>catiscurrent</tt>, and <tt>currentcat</tt> are allowed)</p>

<table><tr>
	<th>Name</th>
	<th>Description</th>
</tr><tr>
	<td>blogid</td>
	<td>ID of the weblog</td>
</tr><tr>
	<td>blogurl</td>
	<td>URL of the blog (as defined in blogsettings)</td>
</tr><tr>
	<td>self</td>
	<td>Current page, without parameters (e.g. <tt>index.php</tt>)</td>
</tr><tr>
	<td>catlink</td>
	<td>a link to the most recent items for a category, which you can embed in a &lt;a href=".."&gt; tag.</td>
</tr><tr>
	<td>catid</td>
	<td>Category ID</td>
</tr><tr>
	<td>catname</td>
	<td>Category name</td>
</tr><tr>
	<td>catdesc</td>
	<td>Category description</td>
</tr><tr>
	<td>catiscurrent</td>
	<td>yes if category is currently selected, no if it is not. Useful to style current category.</td>
</tr><tr>
	<td>currentcat</td>
	<td>Synonym of catiscurrent</td>
</tr></table>

<p><a href="#categorylistexample">View an example</a></p>

</div>

<div class="page"><a name="categorylistexample"></a>
<h1>Templates: Category Lists Example</h1>
<p>
<a href="#templatecategorylists">(go back)</a>
</p>

<h2>Header</h2>
<pre><code>&lt;ul&gt;
  &lt;li&gt;&lt;a href="&lt;blogurl%&gt;"&gt;All&lt;/a&gt;&lt;/li&gt;</code></pre>

<h2>List Item</h2>
<pre><code>&lt;li&gt;&lt;a href="&lt;%catlink%&gt;"&gt;&lt;%catname%&gt;&lt;/a&gt;&lt;/li&gt;</code></pre>

<h2>Footer</h2>
<pre><code>&lt;/ul&gt;</code></pre>

<h2>Results in:</h2>

<ul class="example">
	<li><a href="#categorylistexample">All</a></li>
	<li><a href="#categorylistexample">myCategory</a></li>
	<li><a href="#categorylistexample">yourCategory</a></li>
</ul>

</div>

<div class="page"><a name="templatebloglists"></a>
<h1>Templates: Blog Lists</h1>

<p>The blog lists are formatted as listed below:</p>

<pre>bloglist header
  bloglist listitem (repeated)
bloglist footer</pre>

<p>Available variables in list item field: </p>

<table><tr>
	<th>Name</th>
	<th>Description</th>
</tr><tr>
	<td>bloglink</td>
	<td>URL of the blog (as generated by createBlogIdLink() function)</td>
</tr><tr>
	<td>blogurl</td>
	<td>URL of the blog (as defined in blogsettings)</td>
</tr><tr>
	<td>blogdesc</td>
	<td>Description of the blog</td>
</tr><tr>
	<td>blogname</td>
	<td>Name of the blog (either full or short, depending on skinvar parameter).</td>
</tr></table>

<p>Available variables in header and footer fields: </p>

<table><tr>
	<th>Name</th>
	<th>Description</th>
</tr><tr>
	<td>siteurl</td>
	<td>URL of the site (as defined in global settings)</td>
</tr><tr>
	<td>sitename</td>
	<td>Name of the site (as defined in global settings).</td>
</tr></table>

<p><a href="#bloglistexample">View an example</a></p>

</div>

<div class="page"><a name="bloglistexample"></a>
<h1>Templates: Blog Lists Example</h1>
<p>
<a href="#templatebloglists">(go back)</a>
</p>

<h2>Header</h2>
<pre><code>&lt;ul&gt;
  &lt;li&gt;&lt;a href="&lt;siteurl%&gt;"&gt;&lt;sitename%&gt;&lt;/a&gt;&lt;/li&gt;</code></pre>

<h2>List Item</h2>
<pre><code>&lt;li&gt;&lt;a href="&lt;%bloglink%&gt;"&gt;&lt;%blogname%&gt;&lt;/a&gt;&lt;/li&gt;</code></pre>

<h2>Footer</h2>
<pre><code>&lt;/ul&gt;</code></pre>

<h2>Results in:</h2>

<ul class="example">
	<li><a href="#bloglistexample">My Site</a></li>
	<li><a href="#bloglistexample">mainblog</a></li>
	<li><a href="#bloglistexample">newsblog</a></li>
</ul>

</div>







<div class="page"><a name="templatelocale"></a>
<h1>Templates: Locale</h1>
<p>
This is actually not a template-part, it's a setting. Setting it allows the date and time preferences when to be localized. Names of months and days will be in the desired language, etc.
</p>

<p>
The possible values depend according to which machine Nucleus is running on. Some possible values are
</p>

<ul>
	<li><strong>en</strong>: English</li>
	<li><strong>dutch</strong>: Dutch</li>
	<li>...</li>
</ul>

<p>
More info in the <a href="http://www.opengroup.org/onlinepubs/7908799/xsh/strftime.html" onclick="window.open(this.href);return false;" class="out" title="Open Group specification">Open Group Specification</a> for strftime. (opens a new window)
</p>

<p>
The locale is used for the <a href="#templatedatetime">date and time format</a>, for the <a href="#templatedateheads">dateheaders</a>, and for the <a href="#templatearchivelists">archivelist items</a>
</p>

</div>

<div class="page"><a name="templatedatetime"></a>
<h1>Templates: Date and Time formats</h1>
<p>
These are used to format dates and times into the <code>&lt;%date%&gt;</code> and <code>&lt;%time%&gt;</code> vars (see <a href="#templatevars-overview">template vars</a>). The formatting is done according to the <a href="#templatelocale">locale</a>
</p>

<p>
<a href="#strftime">More info on the available vars</a>. If want to get started quickly, use "%x" to format the date and "%X" to format the time.
</p>

</div>

<div class="page"><a name="templatedateheads"></a>
<h1>Template: Date headers/footers</h1>

<p>
The date header and date footer can contain date and time vars. <a href="#strftime">More info on the available vars</a>. If you want to get started quickly, use "%x" to format the date. The language which is used to format the date, is determined by the <a href="#templatelocale">locale-setting</a> in the template.</p>

<p>
In the date header, the template variable &lt;%%daylink%%&gt; is allowed to insert a link to the archive for that day. <strong>Note the double '%'! It's necessary to avoid %d to be expanded as the current day of the month.</strong> Also, if you just want to add a '%' character somewhere, you should also put it twice ('%%') or it will be gone on your website.
</p>

<p>
Sample for date header:
</p>

<pre>
&lt;div class="day"&gt;
&lt;h1&gt;%d %B&lt;/h1&gt;
</pre>

<p>
Sample for date footer:
</p>

<pre>
&lt;/div&gt;
</pre>

<p>And another example for the date head using daylink</p>

<pre>
&lt;div class="day"&gt;
&lt;h1&gt;%d %B&lt;/h1&gt;
&lt;a href="&lt;%%daylink%%&gt;"&gt;(archive)&lt;/a&gt;
</pre>

</div>

<div class="page"><a name="templatehighlight"></a>
<h1>Templates: Highlight</h1>
<p>
The highlighting is used when performing searches. This is actually used in a regular expression, so you might want to escape some characters by putting a backslash before them. The place where the highlighted word will come, is indicated by "\0".
</p>

<h2>Example</h2>

<pre><code>&lt;span style='background-color:yellow'&gt;\0&lt;/span&gt;</code></pre>

</div>

<div class="page"><a name="templatenothingfound"></a>
<h1>Templates: nothing found</h1>

<p>
Shown when a search has been performed and no results were found.
</p>

<p>Available variables:</p>

<table><tr>
	<th>Name</th>
	<th>Description</th>
</tr><tr>
	<td>blogid</td>
	<td>ID of the weblog</td>
</tr><tr>
	<td>query</td>
	<td>the query that was used in the search</td>
</tr></table>

<h2>Example</h2>

<pre><code>No search results found for &lt;b&gt;&lt;%query%&gt;&lt;/b&gt;</code></pre>

</div>

<div class="page"><a name="templatecommentbody"></a>
<h1>Templates: Comment body</h1>
<p>
This is the part of the template used to display a single comment. In this template-part, <a href="#templatevars-comments" title="Overview of comments-related template variables">comments-related templatevars</a> are available.</p>

<h2>Example</h2>
<pre><code>&lt;h2&gt;Comment by &lt;%userlink%&gt;:&lt;/h2&gt;

&lt;p&gt;&lt;%body%&gt;&lt;/p&gt;

&lt;div class="metadata"&gt;
 (from &lt;%host%&gt; on &lt;%date%&gt; at &lt;%time%&gt;)
&lt;/div&gt;</code></pre>

<p>Result:</p>

<div class="example">
<h4 style="margin: 2px;">Comment by <a href="#templatecommentbody">karma</a>:</h4>
<p style="margin: 2px;">Nice!</p>
<div style="margin:2px;font-size:smaller;">(from host.example.org on 2003-03-02 at 13:30)</div>
</div>

</div>

<div class="page"><a name="templatepopups"></a>
<h1>Templates: Media &amp; Popups</h1>
<p>
These templates are used to format links to popup image windows and media objects (non-pictures). The available variables for each of the templates are described below
</p>

<h2>Popup Link Code</h2>

<table><tr>
	<th>Name</th>
	<th>Description</th>
</tr><tr>
	<td>popuplink</td>
	<td>an &lt;a href... link ready to use</td>
</tr><tr>
	<td>rawpopuplink</td>
	<td>only the url inside href="..."</td>
</tr><tr>
	<td>popupcode</td>
	<td>javascript code to open window</td>
</tr><tr>
	<td>text</td>
	<td>the alternate text (link text)</td>
</tr><tr>
	<td>width</td>
	<td>image width</td>
</tr><tr>
	<td>height</td>
	<td>image width</td>
</tr><tr>
	<td>popuptext</td>
	<td>(=same as text)</td>
</tr><tr>
	<td>link</td>
	<td>direct link to the image (URL)</td>
</tr><tr>
	<td>media</td>
	<td>a non-popup A-tag to the image, ready to use.</td>
</tr></table>


<h2>Inline Image Code</h2>

<table><tr>
	<th>Name</th>
	<th>Description</th>
</tr><tr>
	<td>image</td>
	<td>an IMG-tag, ready to use</td>
</tr><tr>
	<td>link</td>
	<td>direct link to the image (URL)</td>
</tr><tr>
	<td>text</td>
	<td>the alternate text (link text)</td>
</tr><tr>
	<td>width</td>
	<td>image width</td>
</tr><tr>
	<td>height</td>
	<td>image width</td>
</tr><tr>
	<td>media</td>
	<td>an A-tag to the image, ready to use.</td>
</tr></table>

<h2>Media Object Link Code</h2>

<table><tr>
	<th>Name</th>
	<th>Description</th>
</tr><tr>
	<td>media</td>
	<td>an A-tag, ready to use</td>
</tr><tr>
	<td>link</td>
	<td>direct link to the file (URL)</td>
</tr><tr>
	<td>text</td>
	<td>the alternate text (link text)</td>
</tr></table>

</div>

<div class="page"><a name="templatememberextra"></a>
<h1>Templates: Member Extra</h1>
<p>
This is a template you can use to add an extra indication that a comment-author is a member. It ends up in the <code>&lt;%authtext%&gt;</code> variable for use in the <a href="#templatecommentbody">comment body</a>
</p>

<p>Inside this template-part, some <a href="#templatevars-comments" title="Overview of comments-related template variables">comments-related variables</a> are available.</p>

</div>

<div class="page"><a name="templatecommentcontinued"></a>
<h1>Templates: Comments Read More</h1>
<p>
This is the format of the link that will be added at the end of <code>&lt;%short%&gt;</code>, which is a variable for use in the <a href="#templatecommentbody">comment body</a>
</p>

<p>Inside this template-part, some <a href="#templatevars-comments" title="Overview of comments-related template variables">comments-related variables</a> are available (except for the <code>&lt;%short%&gt;</code> variable).</p>

<p>Example:</p>

<pre>
 &lt;a href="&lt;%itemlink%&gt;"&gt;[more]&lt;/a&gt;
</pre>

</div>

<div class="page"><a name="templatecommentwords"></a>
<h1>Templates: commentword</h1>
<p>
Most likely, you'll rather want to write "1 comment" than "1 comment(s)". The "One comment" and "Many comments" template parts can be used for this purpose. They will be used to fill the <code>&lt;%commentword%&gt;</code> variable that you can use elsewhere.
</p>

<p>
If there is only 1 comment, <code>&lt;%commentword%&gt;</code> will be equal to the contents of the "one comment" part. If there are many comments (more than one), <code>&lt;%commentword%&gt;</code> will be equal to the contents of the "two (or more) comments" part.
</p>

<p>
Typical values are "comment" and "comments". <strong>No special variables can be used here</strong>.
</p>
</div>



<div class="page"><a name="templateeditlink"></a>
<h1>Templates: Edit Link</h1>
<p>
This template defines how the <a href="#templatevar-edit">edit-templatevar</a> will be marked up. You can use any of the <a href="#templatevars-overview">template variables</a> here.
</p>

<h2>Example:</h2>

<pre><code>&lt;a href="&lt;%editlink%&gt;"
   onclick="&lt;%editpopupcode%&gt;"&gt;edit&lt;/a&gt;</code></pre>

</div>




<div class="page"><a name="skinpartindex"></a>
<h1>Skins: Main Index</h1>
<p>
This skinpart is used to show the most recent entries of your weblog. It's usually the home page of your site.
</p>

<p>
Very basic buildup for a main index:
</p>

<pre>
&lt;html&gt;
  &lt;head&gt;
    &lt;title&gt;My Weblog&lt;/title&gt;
  &lt;/head&gt;
  &lt;body&gt;

    &lt;h1&gt;My Weblog&lt;/h1&gt;
    &lt;%blog(mytemplate,20)%&gt;

  &lt;/body&gt;
&lt;/html&gt;
</pre>

<p>
	This will show the 20 most recent items of the default weblog (unless overridden), using the 'mytemplate' template.
</p>
</div>


<div class="page"><a name="skinpartitem"></a>
<h1>Skins: Detail Pages</h1>
<p>
These pages are used to show the full items, all comments that were made and a form to add comments.
</p>

<p>
Very basic buildup for a detailed item page:
</p>

<pre>
&lt;html&gt;
  &lt;head&gt;
    &lt;title&gt;My Weblog :: Item&lt;/title&gt;
  &lt;/head&gt;
  &lt;body&gt;

    &lt;h1&gt;Item&lt;/h1&gt;
    &lt;%item(detailed)%&gt;

    &lt;h1&gt;Comments&lt;/h1&gt;
    &lt;%comments(detailed)%&gt;

    &lt;h1&gt;Add Comment&lt;/h1&gt;
    &lt;%commentform%&gt;

  &lt;/body&gt;
&lt;/html&gt;
</pre>

<p>
	This will show the item and comments using the 'detailed' template, and add a standard commentform.
</p>


</div>

<div class="page"><a name="skinpartarchivelist"></a>
<h1>Skins: Archive List</h1>
<p>
An overview of all the months for which archives are available, and links to those archives
</p>

<p>
Very basic buildup for an archive list:
</p>

<pre>
&lt;html&gt;
  &lt;head&gt;
    &lt;title&gt;My Weblog :: Archives&lt;/title&gt;
  &lt;/head&gt;
  &lt;body&gt;

    &lt;h1&gt;Archives&lt;/h1&gt;
    &lt;%archivelist(default)%&gt;

  &lt;/body&gt;
&lt;/html&gt;
</pre>

<p>
	This will show the list of all available archive files, using the 'default' template
</p>

</div>

<div class="page"><a name="skinpartarchive"></a>
<h1>Skins: Archive</h1>
<p>
An archive for one month. Behaves like a main index, but shows all the items from a certain month.
</p>

<p>
Very basic buildup for an archive page:
</p>

<pre>
&lt;html&gt;
  &lt;head&gt;
    &lt;title&gt;My Weblog :: Archive&lt;/title&gt;
  &lt;/head&gt;
  &lt;body&gt;

    &lt;h1&gt;Archive&lt;/h1&gt;
    &lt;%archive(default)%&gt;

  &lt;/body&gt;
&lt;/html&gt;
</pre>

<p>
	This will show the requested archive using the 'default' template
</p>


</div>


<div class="page"><a name="skinpartsearch"></a>
<h1>Skins: Search</h1>
<p>
Used to show search results.
</p>

<p>
Very basic buildup for a searchresults page:
</p>

<pre>
&lt;html&gt;
  &lt;head&gt;
    &lt;title&gt;My Weblog :: Search&lt;/title&gt;
  &lt;/head&gt;
  &lt;body&gt;

    &lt;h1&gt;Search&lt;/h1&gt;
    &lt;%searchform%&gt;

    &lt;h1&gt;Searchresults&lt;/h1&gt;
    &lt;%searchresults(default)%&gt;

  &lt;/body&gt;
&lt;/html&gt;
</pre>

<p>
	This will show search results using the 'default' template.
</p>

</div>

<div class="page"><a name="skinparterror"></a>
<h1>Skins: Errors</h1>
<p>
Used when there is an error
</p>

<pre>
&lt;html&gt;
  &lt;head&gt;
    &lt;title&gt;My Weblog :: Error&lt;/title&gt;
  &lt;/head&gt;
  &lt;body&gt;

    &lt;h1&gt;Error!&lt;/h1&gt;
    &lt;%errormessage%&gt;

    &lt;br /&gt;&lt;br /&gt;

    &lt;a href="javascript:history.back();"&gt;Back&lt;/a&gt;

  &lt;/body&gt;
&lt;/html&gt;
</pre>

<p>
	This will show the error message, plus a link to go back.
</p>

</div>

<div class="page"><a name="skinpartmember"></a>
<h1>Skins: Member</h1>
<p>
Used to show member details.
</p>

<p>
Very basic buildup for a member-detail page:
</p>

<pre>
&lt;html&gt;
  &lt;head&gt;
    &lt;title&gt;My Weblog :: Member details&lt;/title&gt;
  &lt;/head&gt;
  &lt;body&gt;

    &lt;h1&gt;Info about &lt;%member(name)%&gt;&lt;/h1&gt;
    Website:
    &lt;a href="&lt;%member(url)%&gt;"&gt;&lt;%member(url)%&gt;&lt;/a&gt;

    &lt;h1&gt;Send Message&lt;/h1&gt;
    &lt;%membermailform%&gt;

  &lt;/body&gt;
&lt;/html&gt;
</pre>

<p>
	This will show the members name, website address and a mailform.
</p>

</div>


<div class="page"><a name="skinpartimagepopup"></a>
<h1>Skins: Image Popup</h1>
<p>
Used when a media file (image) needs to be shown in a popup window. This skin defines the layout that will be used in that case.
</p>

<p>
Very basic buildup for an imagepopup page:
</p>

<pre>
&lt;html&gt;
&lt;head&gt;
  &lt;title&gt;&lt;%imagetext%&gt;&lt;/title&gt;
  &lt;style type="text/css"&gt;
   img { border: none; }
  &lt;/style&gt;
&lt;/head&gt;
&lt;body&gt;
  &lt;a href="javascript:window.close();"&gt;&lt;%image%&gt;&lt;/a&gt;
&lt;/body&gt;
&lt;/html&gt;
</pre>

</div>


<div class="page"><a name="skinpartspecial"></a>
<h1>Skins: Main Index</h1>
<p>
This skinpart is used to show special, non-blog, content on your site. It can be used to show static content, or to wrap other 
dynamic applications, like forms, inside the skin of your blog. It is accessed by the name of the special skin part, in this way 
(assuming the special skin part is named <code>fred</code>):
</p>
<code>http://www.yoursite.tld/index.php?special=fred</code>

<p>Further discussion of the use of this feature can be found on the support forum: 
<a href="http://forum.nucleuscms.org/viewtopic.php?t=16501" title="Special Skin Parts">Nucleus 3.31 and Static Pages</a>
</p>

<p>
Very basic buildup for a special skin part:
</p>

<pre>
&lt;html&gt;
  &lt;head&gt;
    &lt;title&gt;My Weblog&lt;/title&gt;
  &lt;/head&gt;
  &lt;body&gt;

    &lt;h1&gt;About My Site&lt;/h1&gt;
    &lt;p&gt;This page was published in order 
	to provide a platform to publicize the plight 
	of the peeping-polly parrot whose present 
	prognosis is perturbingly pessimistic.&lt;/p&gt;

  &lt;/body&gt;
&lt;/html&gt;
</pre>

<p>
	This will show the text of the body as indicated above. Also, many SkinVars work on special pages, so you can make 
	the page look just like the other pages and use SkinVars to show an index of the whole site, or a list of members, etc...
</p>
</div>




<div class="page"><a name="shortnames"></a>
<h1>Shortnames &amp; Display Names</h1>
<p>
Weblogs, templates and skin should all have a short name next to the full name or description.
</p>

<p>
A short name consists of <strong>only</strong> the characters a-z and 0-9, and <strong>cannot</strong> contain spaces
</p>

<p>
Display names are used for members. They can contain a-z, A-Z, 0-9 and spaces, but the spaces cannot be placed at the beginning or end of the name.
</p>
</div>






<div class="page"><a name="templatenew"></a>
<h1>Template: 'New' indication</h1>
<p>
When the <a href="#cookies">'last visit' cookie</a> option is activated, the contents of the 'Indication of new item'-template is copied into the &lt;%new%&gt; variable for items that have been added since the last visit. The <code>&lt;%new%&gt;</code> variable can e.g. be used in the <a href="#templateitems">item body</a>-template.
</p>

<p>
When the 'last visit' cookie is disabled, or the item is not 'new', this template part will not be used.
</p>
</div>


<div class="page"><a name="strftime"></a>
<h1>Time variables overview</h1>

<p>The following conversion specifiers are recognized in the format string <small>(taken from the PHP documentation for the strftime function)</small>. More info in the <a href="http://www.opengroup.org/onlinepubs/7908799/xsh/strftime.html" onclick="window.open(this.href);return false;" class="out" title="Open Group specification">Open Group Specification</a></p>

<ul>
	<li><strong>%a</strong> - abbreviated weekday name according to the current locale</li>
	<li><strong>%A</strong> - full weekday name according to the current locale</li>
	<li><strong>%b</strong> - abbreviated month name according to the current locale</li>
	<li><strong>%B</strong> - full month name according to the current locale</li>
	<li><strong>%c</strong> - preferred date and time representation for the current locale</li>
	<li><strong>%d</strong> - day of the month as a decimal number (range 00 to 31)</li>
	<li><strong>%H</strong> - hour as a decimal number using a 24-hour clock (range 00 to 23)</li>
	<li><strong>%I</strong> - hour as a decimal number using a 12-hour clock (range 01 to 12)</li>
	<li><strong>%j</strong> - day of the year as a decimal number (range 001 to 366)</li>
	<li><strong>%m</strong> - month as a decimal number (range 1 to 12)</li>
	<li><strong>%M</strong> - minute as a decimal number</li>
	<li><strong>%p</strong> - either `am' or `pm' according to the given time value, or the corresponding strings for the current locale</li>
	<li><strong>%S</strong> - second as a decimal number</li>
	<li><strong>%U</strong> - week number of the current year as a decimal number, starting with the first Sunday as the first day of the first week</li>
	<li><strong>%W</strong> - week number of the current year as a decimal number, starting with the first Monday as the first day of the first week</li>
	<li><strong>%w</strong> - day of the week as a decimal, Sunday being 0</li>
	<li><strong>%x</strong> - preferred date representation for the current locale without the time</li>
	<li><strong>%X</strong> - preferred time representation for the current locale without the date</li>
	<li><strong>%y</strong> - year as a decimal number without a century (range 00 to 99)</li>
	<li><strong>%Y</strong> - year as a decimal number including the century</li>
	<li><strong>%Z</strong> - time zone or name or abbreviation</li>
	<li><strong>%%</strong> - a literal `%' character</li>
</ul>

</div>

<div class="page"><a name="sendping"></a>
<h1>Ping weblog listing services</h1>
<p>
When updating your weblog, you can choose to send an update notification (ping) to various weblog listing services. They provides a list of recently updated weblogs to everyone who requests it. Lots of websites are using this data, so you might receive some extra hits when enabling the ping.
</p>
<p class="note"><strong>Note:</strong> For this feature to work correctly, you need to fill out both the weblog URL and the weblog name in the blogsettings.
</p>

</div>

<div class="page"><a name="blogsearchable"></a>

<h1>Always include in search</h1>

<p>When the 'include in search' option is selected, the weblog will <strong>always</strong> be included in searches, even if the search is done on another weblog.</p>

<p>As an example, suppose you have two blogs called 'lifelog' and 'linkdump', with the 'include in search' enabled for 'linkdump'. Now, a search query on 'lifelog' will also search through 'linkdump', while a search query on 'linkdump' will only search entries in 'linkdump'</p>


</div>


<div class="page"><a name="convertbreaks"></a>
<h1>Convert Linebreaks</h1>
<p>
By default, Nucleus converts linebreaks in your items to <code>&lt;br /&gt;</code> tags, so a linebreak will also show up in your (X)HTML output
</p>
<p>
Advanced users, or users striving for the semantic web (<tt>br</tt> tags don't add any information, they're just used for markup), might find this feature annoying, and turn this feature off.
</p>
</div>


<div class="page"><a name="media"></a>
<h1>Media</h1>
<p>
Nucleus allows you to upload media files (images, video, sound, ...) to your website
</p>
<p>
Some settings are needed to do this:
</p>
<ul>
	<li><strong>Media dir</strong>: location on the server where the media files will be saved (local filesystem)</li>
	<li><strong>Media URL</strong>: location of the media files</li>
	<li><strong>Allow upload</strong>: It's possible to disable file upload</li>
	<li><strong>Allowed filetypes for upload</strong>: a bunch of extensions uploaded files can have (seperated by commas, case insensitive)</li>
	<li><strong>Max. upload file size</strong>: Puts a limit on the size of uploaded files</li>
	<li><strong>Prefix Media Files</strong>: When this option is turned on, uploaded file will be prefixed with the current date. Uploading a file named 'bunny.jpg' on April 8, 2003 will then result in a file named 20030408-bunny.jpg. The reason why you might want to do this, is when you're uploading tons of files, and don't want problems with duplicate names.</li>
</ul>

<p>
Each member has his own private collection of media files. Next to that, subdirectories that are under the media dir are seen as global collections (shared between members).
</p>

<p>Uploading is only possible when a member is on the team of at least one of the blogs, to prevent abuse.</p>
</div>


<div class="page"><a name="protectmemnames"></a>
<h1>Protect Member Names</h1>
<p>When this option is enabled, non-logged in members cannot add comments using the same name as registered members. The reason to do this would be to avoid guest impersonating members.</p>
</div>


<div class="page"><a name="pluginurl"></a>
<h1>Plugin URL</h1>
<p>This setting is the base URL for plugin admin areas. Usually it will look like the following</p>
<pre>http://hostname.com/nucleus/plugins/</pre>
</div>

<div class="page"><a name="skinsurl"></a>
<h1>Skins URL</h1>
<p>This setting is the base URL for the Nucleus skins directory. Usually it will look like the following</p>
<pre>http://hostname.com/skins/</pre>
</div>

<div class="page"><a name="actionurl"></a>
<h1>Action URL</h1>
<p>This setting is the absolute URL of the <code>action.php</code> script that comes with Nucleus. Usually it will look like the following</p>
<pre>http://hostname.com/actions.php</pre>
</div>



<div class="page"><a name="additem"></a>
<h1>Adding items</h1>
<p>When adding items to a weblog, there are four kinds of template variables that you can use in the body text, title or extended part:</p>
<ul>
	<li><a href="#templatevar-popup">&lt;%popup(...)%&gt;</a> to insert a popup image</li>
	<li><a href="#templatevar-popup">&lt;%image(...)%&gt;</a> to insert an inline image</li>
	<li><a href="#templatevar-popup">&lt;%media(...)%&gt;</a> to insert a media object</li>
</ul>
<p>Usually, these tags are inserted by the 'insert media' button in the JavaScript toolbar</p>


</div>




<div class="page">
<a name="skinvar-referer"></a>
<h1>Skinvar: referer</h1>
<p>Inserts the refering URL (can be empty)</p>
<h2>Arguments</h2>
<p>None</p>
<h2>Skintypes</h2>
<p>all</p>
<h2>Examples</h2>
<pre>
&lt;a href="&lt;%referer%&gt;"&gt;back&lt;/a&gt;
</pre>
</div>


<div class="page">
<a name="skinvar-itemid"></a>
<h1>Skinvar: itemid</h1>
<p>Inserts the ID of the currently selected item</p>
<h2>Arguments</h2>
<p>None</p>
<h2>Skintypes</h2>
<p>item</p>
<h2>Examples</h2>
<pre>
&lt;%itemid%&gt;
</pre>
</div>


<div class="page">
<a name="skinvar-itemlink"></a>

<h1>Skinvar: itemlink</h1>

<p>Adds a permanent link for the item.</p>

<h2>Arguments</h2>

<p>
	Optional
	<ul>
		<li><strong><em>linktext</em></strong>: when present, a full <code>&lt;a href...</code> tag will be outputted, rather than a raw link</li>
	</ul>
</p>
<h2>Skintypes</h2>

<p>item</p>

<h2>Examples</h2>

<pre>
&lt;%itemlink%&gt;
</pre>
</div>

<div class="page">
<a name="skinvar-itemtitle"></a>
<h1>Skinvar: itemtitle</h1>
<p>Inserts the title of the item, with HTML-stripped off and entities encoded</p>
<h2>Arguments</h2>
<p>None</p>
<h2>Skintypes</h2>
<p>item</p>
<h2>Examples</h2>
<pre>
&lt;%itemtitle%&gt;
</pre>
</div>


<div class="page">
<a name="skinvar-archivedate"></a>
<h1>Skinvar: archivedate</h1>
<p>Inserts a formatted date for an archive date. Using no parameters, this will either insert '15 august 2002' or 'august 2002' if the archive is for august 2002</p>
<h2>Arguments</h2>
<ul>
	<li>Optional
		<table><tr>
			<th>Name</th>
			<th>Value</th>
		</tr><tr>
			<td>Locale</td>
			<td><a href="#templatelocale">Locale</a> in which the date must be formatted</td>
		</tr><tr>
			<td>Format</td>
			<td>Date format (<a href="#strftime">strftime variables</a>)</td>
		</tr></table>
	</li>
</ul>
<h2>Skintypes</h2>
<p>archive</p>
<h2>Examples</h2>
<pre>
Archive for &lt;%archivedate%&gt;
Archive for &lt;%archivedate(dutch)%&gt;
Archive for &lt;%archivedate(en,%B %Y)%&gt;
</pre>
</div>



<div class="page">
<a name="skinvar-blog"></a>
<h1>Skinvar: blog</h1>

<p>
Inserts the most recently added items of the currently active blog (usually the default one) into the skin.
</p>

<h2>Arguments</h2>
<p>
	Required:
	<ul>
		<li><strong>template</strong>: name of the template to use</li>
	</ul>
	Optional:
	<ul>
		<li><strong><em>amount</em></strong>: the amount of items to show (default = 10). Can also contain an offset telling Nucleus to start only from the given item. e.g. <code>10(5)</code> shows 10 items starting from item 5</li>
		<li><strong><em>category</em></strong>: name of the category to show</li>
	</ul>
</p>

<h2>Skintypes</h2>

<p>
index, item, archive, archivelist, search
</p>

<h2>Examples</h2>

<pre>
&lt;%blog(default,15)%&gt;
&lt;%blog(default,5(15))%&gt;
&lt;%blog(mytemplate)%&gt;
&lt;%blog(mytemplate,5,mycategory)%&gt;
</pre>

</div>

<div class="page">
<a name="skinvar-bloglist"></a>
<h1>Skinvar: bloglist</h1>

<p>
Shows a list of all blogs that are defined in your Nucles CMS.
</p>

<h2>Arguments</h2>
<p>
	Required:
	<ul>
		<li><strong>template</strong>: name of the template to use</li>
	</ul>
	Optional:
	<ul>
		<li><strong>bnametype</strong>: whether the Blog Name (<code>name</code>) or the Short Blog Name (<code>shortname</code>) of the Blog is used. Default setting is the Blog name (<code>name</code>).</li>
	</ul>
	<ul>
		<li><strong>orderby</strong>: (3.40) Attribute of the blog used for determinig the order in which the blogs are listed. Supported values are <code>number</code>, <code>name</code>, <code>shortname</code>, <code>description</code>. Default is <code>number</code>.</li>
	</ul>
	<ul>
		<li><strong>direction</strong>: (3.40) Direction of the sorting, <code>asc</code> for ascending order, or <code>desc</code> for descending order. Default is <code>asc</code>.
	</ul>
</p>

<h2>Skintypes</h2>

<p>
all
</p>

<h2>Examples</h2>

<pre>
&lt;%bloglist(default/index)%&gt;
&lt;%bloglist(default/index,name)%&gt; 
&lt;%bloglist(default/index,shortname)%&gt;
&lt;%bloglist(default/index,name,name,asc)%&gt; 
</pre>

</div>



<div class="page">
<a name="skinvar-otherblog"></a>
<h1>Skinvar: otherblog</h1>

<p>
Inserts the most recently added items of a given blog into the skin.
</p>

<h2>Arguments</h2>
<p>
	Required:
	<ul>
		<li><strong>blogname</strong>: name of the blog to show</li>
		<li><strong>template</strong>: name of the template to use</li>
	</ul>
	Optional:
	<ul>
		<li><strong><em>amount</em></strong>: the amount of items to show (default = 10). Can also contain an offset telling Nucleus to start only from the given item. e.g. <code>10(5)</code> shows 10 items starting from item 5</li>
		<li><strong><em>category</em></strong>: name of the category to show</li>
	</ul>
</p>

<h2>Skintypes</h2>

<p>
all
</p>

<h2>Examples</h2>

<pre>
&lt;%otherblog(myblog,default,15)%&gt;
&lt;%otherblog(yourblog,mytemplate)%&gt;
&lt;%otherblog(yourblog,mytemplate,15,mycategory)%&gt;
&lt;%otherblog(yourblog,mytemplate,5(15),mycategory)%&gt;
</pre>

</div>









<div class="page">
<a name="skinvar-item"></a>
<h1>Skinvar: item</h1>

<p>
Shows the currently selected item (without comments) using a given template
</p>

<h2>Arguments</h2>
<ul>
	<li><strong>template</strong>: name of the template to use</li>
</ul>

<h2>Skintypes</h2>

<p>
item
</p>

<h2>Examples</h2>

<pre>
&lt;%item(mytemplate)%&gt;
</pre>

</div>









<div class="page">
<a name="skinvar-comments"></a>
<h1>Skinvar: comments</h1>

<p>
Shows the comments for the currently selected item using a given template.
</p>

<h2>Arguments</h2>
<ul>
	<li><strong>template</strong>: name of the template to use</li>
</ul>

<h2>Skintypes</h2>

<p>
item
</p>

<h2>Examples</h2>

<pre>
&lt;%comments(mytemplate)%&gt;
</pre>

</div>







<div class="page">
<a name="skinvar-archive"></a>
<h1>Skinvar: archive</h1>

<p>
Shows the archive for the selected month and the selected blog (usually the default one), using a given template
</p>

<h2>Arguments</h2>
<p>
	Required
	<ul>
		<li><strong>template</strong>: name of the template to use</li>
	</ul>
	Optional
	<ul>
		<li><strong><em>category</em></strong>: name of the category to show</li>
	</ul>
</p>

<h2>Skintypes</h2>

<p>
archive
</p>

<h2>Examples</h2>

<pre>
&lt;%archive(mytemplate)%&gt;
&lt;%archive(mytemplate,mycategory)%&gt;
</pre>

</div>




<div class="page">
<a name="skinvar-otherarchive"></a>
<h1>Skinvar: otherarchive</h1>

<p>
Shows the archive for the selected month, using the given blog and template
</p>

<h2>Arguments</h2>
<p>
	Required
	<ul>
		<li><strong>blogname</strong>: name of the blog to use</li>
		<li><strong>template</strong>: name of the template to use</li>
	</ul>
	Optional
	<ul>
		<li><strong><em>category</em></strong>: name of the category to show</li>
	</ul>
</p>

<h2>Skintypes</h2>

<p>
archive
</p>

<h2>Examples</h2>

<pre>
&lt;%otherarchive(myblog,mytemplate)%&gt;
&lt;%otherarchive(myblog,mytemplate,mycategory)%&gt;
</pre>

</div>







<div class="page">
<a name="skinvar-archivelist"></a>
<h1>Skinvar: archivelist</h1>

<p>
Shows the list of available archives for the currently selected blog (usually the default one), using a given template
</p>

<h2>Arguments</h2>
<p>
	Required
	<ul>
		<li><strong>template</strong>: name of the template to use</li>
	</ul>
	Optional
	<ul>
		<li><strong><em>category</em></strong>: name of the category to show</li>
		<li><strong><em>limit</em></strong>: limits the amount of links shown (e.g. if you only want to show links to the past 3 months)</li>
	</ul>
</p>

<h2>Skintypes</h2>

<p>
index, archive, archivelist, search, item
</p>
</div>

<div class="page">
<a name="skinvar-archivedaylist"></a>
<h1>Skinvar: archivedaylist</h1>

<p>
The same as the <a href="#skinvar-archivelist">archivelist</a> skinvar, but shows an entry for each <em>day</em> instead of for each <em>month</em>
</p>

<h2>Arguments</h2>
<p>
	Required
	<ul>
		<li><strong>template</strong>: name of the template to use</li>
	</ul>
	Optional
	<ul>
		<li><strong><em>category</em></strong> name of the category to show</li>
		<li><strong><em>limit</em></strong>: limits the amount of links shown (e.g. if you only want to show links to the past 3 months)</li>
	</ul>
</p>

<h2>Skintypes</h2>

<p>
index, archive, archivelist, search, item
</p>


<h2>Examples</h2>

<pre>
&lt;%archivedaylist(mytemplate)%&gt;
&lt;%archivedaylist(mytemplate,mycategory)%&gt;
</pre>

</div>


<div class="page">
<a name="skinvar-otherarchivedaylist"></a>
<h1>Skinvar: otherarchivedaylist</h1>

<p>
The same as the <a href="#skinvar-otherarchivelist">otherarchivelist</a> skinvar, but shows an entry for each <em>day</em> instead of for each <em>month</em>

</p>

<h2>Arguments</h2>
<p>
	Required
	<ul>
		<li><strong>blogname</strong>: name of the blog</li>
		<li><strong>template</strong>: name of the template to use</li>
	</ul>
	Optional
	<ul>
		<li><strong><em>category</em></strong>: name of the category to show</li>
	</ul>
</p>

<h2>Skintypes</h2>

<p>
all
</p>

<h2>Examples</h2>

<pre>
&lt;%otherarchivedaylist(yourblog,mytemplate)%&gt;
&lt;%otherarchivedaylist(yourblog,mytemplate,mycategory)%&gt;
</pre>

</div>

<div class="page">
<a name="skinvar-archiveyearlist"></a>
<h1>Skinvar: archiveyearlist</h1>

<p>
The same as the <a href="#skinvar-archivelist">archivelist</a> skinvar, but shows an entry for each <em>year</em> instead of for each <em>month</em>
</p>

<h2>Arguments</h2>
<p>
	Required
	<ul>
		<li><strong>template</strong>: name of the template to use</li>
	</ul>
	Optional
	<ul>
		<li><strong><em>category</em></strong> name of the category to show</li>
		<li><strong><em>limit</em></strong>: limits the amount of links shown (e.g. if you only want to show links to the past 3 years)</li>
	</ul>
</p>

<h2>Skintypes</h2>

<p>
index, archive, archivelist, search, item
</p>


<h2>Examples</h2>

<pre>
&lt;%archiveyearlist(mytemplate)%&gt;
&lt;%archiveyearlist(mytemplate,mycategory)%&gt;
</pre>

</div>


<div class="page">
<a name="skinvar-otherarchiveyearlist"></a>
<h1>Skinvar: otherarchiveyearlist</h1>

<p>
The same as the <a href="#skinvar-otherarchivelist">otherarchivelist</a> skinvar, but shows an entry for each <em>year</em> instead of for each <em>month</em>

</p>

<h2>Arguments</h2>
<p>
	Required
	<ul>
		<li><strong>blogname</strong>: name of the blog</li>
		<li><strong>template</strong>: name of the template to use</li>
	</ul>
	Optional
	<ul>
		<li><strong><em>category</em></strong>: name of the category to show</li>
	</ul>
</p>

<h2>Skintypes</h2>

<p>
all
</p>

<h2>Examples</h2>

<pre>
&lt;%otherarchiveyearlist(yourblog,mytemplate)%&gt;
&lt;%otherarchiveyearlist(yourblog,mytemplate,mycategory)%&gt;
</pre>

</div>



<div class="page">
<a name="skinvar-otherarchivelist"></a>
<h1>Skinvar: otherarchivelist</h1>

<p>
Shows the list of available archives for a given blog, using a given template
</p>

<h2>Arguments</h2>
<p>
	Required
	<ul>
		<li><strong>blogname</strong>: name of the blog</li>
		<li><strong>template</strong>: name of the template to use</li>
	</ul>
	Optional
	<ul>
		<li><strong><em>category</em></strong>: name of the category to show</li>
	</ul>
</p>

<h2>Skintypes</h2>

<p>
all
</p>

<h2>Examples</h2>

<pre>
&lt;%otherarchivelist(yourblog,mytemplate)%&gt;
&lt;%otherarchivelist(yourblog,mytemplate,mycategory)%&gt;
</pre>

</div>



<div class="page">
<a name="skinvar-categorylist"></a>
<h1>Skinvar: categorylist</h1>

<p>
Inserts a list of categories for a blog (defaults to the currently selected blog), using a given template
</p>

<h2>Arguments</h2>
<p>
	Required
	<ul>
		<li><strong>template</strong>: name of the template to use</li>
	</ul>
	Optional
	<ul>
		<li><strong><em>blogname</em></strong>: short name of the blog to use</li>
	</ul>
</p>

<h2>Skintypes</h2>

<p>
index, archive, archivelist, search, item, [error, member, special if blogname parameter specified]
</p>

<h2>Examples</h2>

<pre>
&lt;%categorylist(mytemplate)%&gt;
&lt;%categorylist(mytemplate,myweblog)%&gt;
</pre>

</div>



<div class="page">
<a name="skinvar-category"></a>
<h1>Skinvar: category</h1>

<p>
Inserts some information about the currently selected category. When no category is selected, does nothing.
</p>

<h2>Arguments</h2>
<p>
	Optional
	<ul>
		<li><strong><em>type</em></strong>: What information to include. Can be <b>name</b> (default), <b>desc</b> or <b>id</b></li>
	</ul>
</p>

<h2>Skintypes</h2>

<p>
all
</p>

<h2>Examples</h2>

<pre>
&lt;%category%&gt;
&lt;%category(id)%&gt;
&lt;%category(desc)%&gt;
&lt;%category(name)%&gt;
</pre>

</div>


<div class="page">
<a name="skinvar-ifcat"></a>
<h1>Skinvar: ifcat</h1>

<p class="deprecated">Deprecated as of Nucleus v2.0. Use <a href="#skinvar-if">&lt;%if(category)%&gt;</a> instead.</p>

<h2>Arguments</h2>
<p>
	None
	<ul>
		<li><em>text</em>: Text to show</li>
	</ul>
</p>

<h2>Skintypes</h2>

<p>
all
</p>

<h2>Examples</h2>

<pre>
&lt;%ifcat(Current Category: )%&gt;&lt;%category%&gt;
</pre>

</div>




<div class="page">
<a name="skinvar-searchresults"></a>
<h1>Skinvar: searchresults</h1>

<p>
Shows the searchresult for the current query
</p>

<h2>Arguments</h2>
<p>
	Required:
	<ul>
		<li><strong>template</strong>: name of the template to use</li>
	</ul>
	Optional:
	<ul>
		<li><strong><em>maxresults</em></strong>: maximum amount of results to show</li>
	</ul>
</p>

<h2>Skintypes</h2>

<p>
search
</p>

<h2>Examples</h2>

<pre>
&lt;%searchresults(mytemplate)%&gt;
</pre>

</div>




<div class="page">
<a name="skinvar-othersearchresults"></a>
<h1>Skinvar: othersearchresults</h1>

<p>
Shows the searchresult in a give blog for the current query, using the given template
</p>

<h2>Arguments</h2>
<p>
	Required:
	<ul>
		<li><strong>blogname</strong>: name of the blog to use</li>
		<li><strong>template</strong>: name of the template to use</li>
	</ul>
	Optional:
	<ul>
		<li><strong><em>maxresults</em></strong>: maximum amount of results to show</li>
	</ul>
</p>

<h2>Skintypes</h2>

<p>
search
</p>

<h2>Examples</h2>

<pre>
&lt;%othersearchresults(myblog,mytemplate)%&gt;
</pre>

</div>







<div class="page">
<a name="skinvar-query"></a>
<h1>Skinvar: query</h1>

<p>
Inserts the current search query.
</p>

<h2>Arguments</h2>
<p>
None
</p>

<h2>Skintypes</h2>

<p>
search
</p>

<h2>Examples</h2>

<pre>
&lt;%query%&gt;
</pre>

</div>








<div class="page">
<a name="skinvar-version"></a>
<h1>Skinvar: version</h1>

<p>Inserts the current Nucleus version.</p>

<h2>Arguments</h2>

<p>
None
</p>

<h2>Skintypes</h2>

<p>
all
</p>

<h2>Examples</h2>

<pre>
&lt;%version%&gt;
</pre>

</div>


<div class="page">
<a name="skinvar-charset"></a>
<h1>Skinvar: charset</h1>

<p>Inserts the character set encoding used by the current language file.</p>

<h2>Arguments</h2>

<p>
None
</p>

<h2>Skintypes</h2>

<p>
all
</p>

<h2>Examples</h2>

<pre>
&lt;%charset%&gt;
</pre>

</div>





<div class="page">
<a name="skinvar-previtem"></a>
<h1>Skinvar: previtem</h1>

<p>
Inserts the ID of the previous item in the blog
</p>

<h2>Arguments</h2>
<p>None</p>

<h2>Skintypes</h2>

<p>
item
</p>

<h2>Examples</h2>

<pre>
&lt;%previtem%&gt;
</pre>

</div>






<div class="page">
<a name="skinvar-nextitem"></a>
<h1>Skinvar: nextitem</h1>

<p>
Inserts the ID of the next item in the blog
</p>

<h2>Arguments</h2>
<p>None</p>

<h2>Skintypes</h2>

<p>
item
</p>

<h2>Examples</h2>

<pre>
&lt;%nextitem%&gt;
</pre>

</div>


<div class="page">
<a name="skinvar-nextitemtitle"></a>
<h1>Skinvar: nextitemtitle</h1>

<p>
Inserts the title of the next item in the blog
</p>

<h2>Arguments</h2>
<p>None</p>

<h2>Skintypes</h2>

<p>
item
</p>

<h2>Examples</h2>

<pre>
&lt;%nextitemtitle%&gt;
</pre>

</div>


<div class="page">
<a name="skinvar-previtemtitle"></a>
<h1>Skinvar: previtemtitle</h1>

<p>
Inserts the title of the previous item in the blog
</p>

<h2>Arguments</h2>
<p>None</p>

<h2>Skintypes</h2>

<p>
item
</p>

<h2>Examples</h2>

<pre>
&lt;%previtemtitle%&gt;
</pre>

</div>




<div class="page">
<a name="skinvar-prevarchive"></a>
<h1>Skinvar: prevarchive</h1>

<p>
Inserts the <code>archive</code> attribute that corresponds to the archive of either 1 day or 1 month back. This value can be used inside URLs to select an archive.
</p>

<ul>
	<li>If the shown archive is for one specific day, the value has the form <code>YYYY-MM-DD</code></li>
	<li>If the shown archive is for a full month, the value has the form <code>YYYY-MM</code></li>
</ul>

<h2>Arguments</h2>
<p>None</p>

<h2>Skintypes</h2>

<p>
archive
</p>

<h2>Examples</h2>

<pre><code>&lt;a href="index.php?archive=&lt;%prevarchive%&gt;&gt;....</code></pre>

</div>






<div class="page">
<a name="skinvar-nextarchive"></a>
<h1>Skinvar: nextarchive</h1>

<p>
Inserts the <code>archive</code> attribute that corresponds to the archive of either 1 day or 1 month further in time. This value can be used inside URLs to select an archive.
</p>

<ul>
	<li>If the shown archive is for one specific day, the value has the form <code>YYYY-MM-DD</code></li>
	<li>If the shown archive is for a full month, the value has the form <code>YYYY-MM</code></li>
</ul>

<h2>Arguments</h2>
<p>None</p>

<h2>Skintypes</h2>

<p>
archive
</p>

<h2>Examples</h2>

<pre><code>&lt;a href="index.php?archive=&lt;%nextarchive%&gt;&gt;....</code></pre>

</div>


<div class="page">
<a name="skinvar-archivetype"></a>
<h1>Skinvar: archivetype</h1>

<p>
Either <tt>day</tt> or <tt>month</tt>, indicating which type of archive is currently being shown
</p>

<h2>Arguments</h2>
<p>None</p>

<h2>Skintypes</h2>

<p>
archive
</p>

</div>





<div class="page">
<a name="skinvar-todaylink"></a>
<h1>Skinvar: todaylink</h1>

<p>
Inserts a link to the main page of the weblog. Takes into account the currently selected blog and category.
</p>

<h2>Arguments</h2>
<p>
	Optional
	<ul>
		<li><strong><em>linktext</em></strong>: when present, a full <code>&lt;a href...</code> tag will be outputted, rather than a raw link</li>
	</ul>
</p>


<h2>Skintypes</h2>

<p>
all
</p>

<h2>Examples</h2>

<pre>
&lt;%todaylink%&gt;
</pre>

</div>







<div class="page">
<a name="skinvar-archivelink"></a>
<h1>Skinvar: archivelink</h1>

<p>
Inserts a link to the archive for the currently selected blog and category (or the default blog when no blog selected)
</p>

<h2>Arguments</h2>

<p>
	Optional
	<ul>
		<li><strong><em>linktext</em></strong>: when present, a full <code>&lt;a href...</code> tag will be outputted, rather than a raw link</li>
	</ul>
</p>


<h2>Skintypes</h2>

<p>
all
</p>

<h2>Examples</h2>

<pre>
&lt;%archivelink%&gt;
</pre>

</div>






<div class="page">
<a name="skinvar-nextlink"></a>
<h1>Skinvar: nextlink</h1>

<p>
Inserts a link to the next item (on item pages) or to the next archive (on archive pages)
</p>

<h2>Arguments</h2>
<p>
	Optional
	<ul>
		<li><strong><em>linktext</em></strong>: when present, a full <code>&lt;a href...</code> tag will be outputted, rather than a raw link</li>
		<li><strong><em>amount</em></strong>: for search and index skins: the amount of items to go forward/backward</li>
		<li><strong><em>recount</em></strong>: for search and index skins: set to yes to force extra query to recount items on page. 
		This is useful for more complex pages where the blog skinvar may be called multiple times because of the use of the offset. 
		Try setting this if nextlink seems to be not advancing the expected number of items.</li>
	</ul>
</p>


<h2>Skintypes</h2>

<p>
item, archive, search, index
</p>

<h2>Examples</h2>

<pre>
&lt;%nextlink%&gt;
&lt;%nextlink(Next Page,10)%&gt;
&lt;%nextlink(,10)%&gt;
&lt;%nextlink(,10,yes)%&gt;
</pre>

</div>








<div class="page">
<a name="skinvar-prevlink"></a>
<h1>Skinvar: prevlink</h1>

<p>
Inserts a link to the previous item (on item pages) or to the previous archive (on archive pages). For search and index pages
</p>

<h2>Arguments</h2>
<p>
	Optional
	<ul>
		<li><strong><em>linktext</em></strong>: when present, a full <code>&lt;a href...</code> tag will be outputted, rather than a raw link</li>
		<li><strong><em>amount</em></strong>: for search and index skins: the amount of items to go forward/backward</li>
	</ul>
</p>

<h2>Skintypes</h2>

<p>
item, archive, search, index
</p>

<h2>Examples</h2>

<pre>
&lt;%prevlink%&gt;
</pre>

</div>








<div class="page">
<a name="skinvar-errormessage"></a>
<h1>Skinvar: errormessage</h1>

<p>
Inserts the message corresponding to the error that occurred
</p>

<h2>Arguments</h2>
<p>None</p>

<h2>Skintypes</h2>

<p>
error
</p>

<h2>Examples</h2>

<pre>
&lt;%errormessage%&gt;
</pre>

</div>








<div class="page">
<a name="skinvar-imagetext"></a>
<h1>Skinvar: imagetext</h1>

<p class="deprecated">This skinvar is deprecated since Nucleus v2.0. You should use <a href="#skinvar-image"><code>&lt;%image(caption)%&gt;</code></a> instead</p>

<p>
Inserts the caption text for a popup image
</p>

<h2>Arguments</h2>
<p>None</p>

<h2>Skintypes</h2>

<p>
imagepopup
</p>

<h2>Examples</h2>

<pre>
&lt;%imagetext%&gt;
</pre>

</div>



<div class="page">
<a name="skinvar-image"></a>
<h1>Skinvar: image</h1>

<p>
Inserts the selected image (for popup images)
</p>

<h2>Arguments</h2>

<p>Optional</p>
<ul>
	<li>
		<em>type</em>
		<table><tr>
			<td><strong>imgtag</strong> (default)</td>
			<td>Full XHTML <code>&lt;img ... /&gt;</code> tag</td>
		</tr><tr>
			<td><strong>url</strong></td>
			<td>Image file URL</td>
		</tr><tr>
			<td><strong>width</strong></td>
			<td>image width</td>
		</tr><tr>
			<td><strong>height</strong></td>
			<td>image height</td>
		</tr><tr>
			<td><strong>caption</strong></td>
			<td>image caption (text to go with image)</td>
		</tr></table>
	</li>
</ul>

<h2>Skintypes</h2>

<p>
imagepopup
</p>

<h2>Examples</h2>

<pre>
&lt;%image%&gt;
</pre>

</div>


<div class="page">
<a name="skinvar-vars"></a>
<h1>Skinvar: vars</h1>

<p class="deprecated">This skinvar is deprecated since Nucleus v2.0. It's a small pain to insert this HTML yourself using the <a href="#skinvar-itemid">itemid skinvar</a></p>

<p>
Inserts a hidden form-input field with the itemid.
</p>

<code>&lt;input type="hidden" name="itemid" value="<strong>1234</strong>" /&gt;</code>

<h2>Arguments</h2>
<p>None</p>

<h2>Skintypes</h2>

<p>
item
</p>


</div>






<div class="page">
<a name="skinvar-sitevar"></a>
<h1>Skinvar: sitevar</h1>

<p>
Includes a site variable
</p>

<h2>Arguments</h2>
<ul>
	<li><strong>type</strong>: name of the variable to show:
	<ul>
		<li><em>url</em>: URL of the site</li>
		<li><em>name</em>: Name of the site</li>
		<li><em>admin</em>: E-mail address of the administrator</li>
	</ul>
	</li>
</ul>

<h2>Skintypes</h2>

<p>
all
</p>

<h2>Examples</h2>

<pre>
&lt;%sitevar(name)%&gt;
&lt;%sitevar(url)%&gt;
&lt;a href="mailto:&lt;%sitevar(email)%&gt;"&gt;Admin&lt;/a&gt;
</pre>

</div>






<div class="page">
<a name="skinvar-blogsetting"></a>
<h1>Skinvar: blogsetting</h1>

<p>
Inserts a setting specific to the currently selected blog (usually the default one)
</p>

<h2>Arguments</h2>
<ul>
	<li><strong>type</strong>: which setting to add
	    <ul>
	    	<li><em>id</em>: ID of the blog</li>
	    	<li><em>url</em>: URL of the blog</li>
	    	<li><em>name</em>: Name of the blog (long name)</li>
	    	<li><em>desc</em>: Description of the blog</li>
	    	<li><em>short</em>: Short name of the blog</li>
	    </ul>
	</li>
</ul>

<h2>Skintypes</h2>

<p>
index, archive, archivelist, search, item, member
</p>

<h2>Examples</h2>

<pre>
&lt;%blogsetting(name)%&gt;
&lt;%blogsetting(id)%&gt;
&lt;%blogsetting(desc)%&gt;
&lt;a href="&lt;%blogsetting(url)%&gt;"&gt;...&lt;/a&gt;
</pre>

</div>






<div class="page">
<a name="skinvar-member"></a>
<h1>Skinvar: member</h1>

<p>
Inserts some info about on the currently logged in member. On member detail pages, extra options are available to show the same information for the requested member.
</p>

<p>When the visitor is not logged in, the <em>your...</em> parameters will insert nothing</p>

<h2>Arguments</h2>
<ul>
	<li><strong>type</strong>: which information to show.
		<p>Information on the logged in member:</p>
	    <ul>
	    	<li><em>yourname</em>: nickname of the member (the one used to login)</li>
	    	<li><em>yourrealname</em>: full name of the member</li>
	    	<li><em>yournotes</em>: extra information a member can set for him/herself</li>
	    	<li><em>yoururl</em>: URL of the members website</li>
	    	<li><em>youremail</em>: email address </li>
	    	<li><em>yourid</em>: ID</li>
	    	<li><em>yourprofileurl</em>: URL of the members profile (member details) page</li>
	    </ul>
	    <p>Information on the requested member (only available on member detail pages):</p>
	    <ul>
	    	<li><em>name</em>: nickname of the member (the one used to login)</li>
	    	<li><em>realname</em>: full name of the member</li>
	    	<li><em>notes</em>: extra information a member can set for him/herself</li>
	    	<li><em>url</em>: URL of the members website</li>
	    	<li><em>email</em>: email address of the member</li>
	    	<li><em>id</em>: ID</li>
	    </ul>
	</li>
</ul>

<h2>Skintypes</h2>

<p>
all
</p>

<h2>Examples</h2>

<pre><code>
&lt;%if(loggedin)%&gt;
you are &lt;%member(yourrealname)%&gt;
&lt;%endif%&gt;
</code></pre>

</div>






<div class="page">
<a name="skinvar-preview"></a>
<h1>Skinvar: preview</h1>

<p>
Inserts an item-preview into the page, using a given template (to be used in conjunction with <a href="#skinvar-additemform">additemform</a>)
</p>

<h2>Arguments</h2>
<ul>
	<li><strong>template</strong>: name of the template to be used</li>
</ul>

<h2>Skintypes</h2>

<p>
index
</p>

<h2>Examples</h2>

<pre>
&lt;%preview(mytemplate)%&gt;
</pre>

</div>



<div class="page">
<a name="skinvar-adminurl"></a>
<h1>Skinvar: adminurl</h1>

<p>Inserts the full URL to the Admin Area</p>

<h2>Arguments</h2>
<p>None</p>

<h2>Skintypes</h2>

<p>
all
</p>

<h2>Examples</h2>

<pre>
&lt;a href="&lt;%adminurl%&gt;"&gt;Admin Area&lt;/a&gt;
</pre>

</div>




<div class="page">
<a name="skinvar-additemform"></a>
<h1>Skinvar: additemform</h1>

<p>
Shows an add-item form for the currently selected blog (usually the default one). Mostly used in conjunction with <a href="#skinvar-preview">preview</a>
</p>

<h2>Arguments</h2>
<p>None</p>

<h2>Skintypes</h2>

<p>
index
</p>

<h2>Examples</h2>

<pre>
&lt;%additemform%&gt;
</pre>

</div>






<div class="page">
<a name="skinvar-include"></a>
<h1>Skin/Templatevar: include</h1>

<p>
Includes a textfile into the output. The contents of the file is not parsed in any way, so you cannot use skin/templatevars or use PHP code (see <a href="#skinvar-parsedinclude">parsedinclude</a> and <a href="#skinvar-phpinclude">phpinclude</a> if you want parsed includes)
</p>

<h2>Arguments</h2>
<ul>
	<li><strong>filename</strong>: the name of the file to be included (either relative to the position of index.php, or absolute). Note that an URL can also be used here.</li>
</ul>

<h2>Notes</h2>
<ul>
	<li>This tag is affected by the <a href="#parser-properties">parser settings <code>IncludeMode</code> and <code>IncludePrefix</code></a></li>
</ul>

<h2>Skintypes</h2>

<p>
all
</p>

<h2>Examples</h2>

<pre>
&lt;%include(filename.txt)%&gt;
&lt;%include(/home/user/myself/filename.txt)%&gt;
&lt;%include(http://mydomain.com/filename.html)%&gt;
</pre>

</div>







<div class="page">
<a name="skinvar-phpinclude"></a>
<h1>Skin/Templatevar: phpinclude</h1>

<p>
Includes a php-file into the output. The contents of the file is parsed by the PHP parser, so be careful. Nucleus skin/templatevars are <b>not</b> parsed! (see <a href="#skinvar-parsedinclude">parsedinclude</a> and <a href="#skinvar-include">include</a> for other include options).
</p>

<h2>Arguments</h2>
<ul>
	<li><strong>filename</strong>: the name of the file to be included (either relative to the position of index.php, or absolute)</li>
</ul>

<h2>Notes</h2>
<ul>
	<li>This tag is affected by the <a href="#parser-properties">parser settings <code>IncludeMode</code> and <code>IncludePrefix</code></a></li>
	<li>Your file will be included using the standard php <code>include()</code> command. This command will be called from <em>inside</em> a class method, so <strong>you'll need to declare which global variables you want to access</strong> yourself. Most of the <a href="#skinvar-phpinclude-vars">standard variables</a> are automatically declared global by Nucleus itself.</li>
</ul>

<h2>Skintypes</h2>

<p>
all
</p>

<h2>Examples</h2>

<pre><code>&lt;%phpinclude(filename.php)%&gt;
&lt;%phpinclude(/home/user/myself/filename.php)%&gt;</code></pre>

</div>



<div class="page">
<a name="skinvar-phpinclude-vars"></a>
<h1>Skin/Templatevar: phpinclude : vars</h1>

<p>
The following global variables are accessible from within files included by the <a href="#skinvar-phpinclude">phpinclude</a> skin/templatevar:
</p>

<p>
$GATEWAY_INTERFACE, $SERVER_NAME, $SERVER_SOFTWARE
<br />$SERVER_PROTOCOL, $REQUEST_METHOD, $QUERY_STRING
<br />$DOCUMENT_ROOT, $HTTP_ACCEPT, $HTTP_ACCEPT_CHARSET
<br />$HTTP_ACCEPT_ENCODING, $HTTP_ACCEPT_LANGUAGE
<br />$HTTP_CONNECTION, $HTTP_HOST, $HTTP_REFERER
<br />$HTTP_USER_AGENT, $REMOTE_ADDR, $REMOTE_PORT
<br />$SCRIPT_FILENAME, $SERVER_ADMIN, $SERVER_PORT
<br />$SERVER_SIGNATURE, $PATH_TRANSLATED, $SCRIPT_NAME
<br />$REQUEST_URI, $argv, $argc, $PHP_SELF
<br />$HTTP_COOKIE_VARS, $HTTP_GET_VARS, $HTTP_POST_VARS
<br />$HTTP_POST_FILES, $HTTP_ENV_VARS, $HTTP_SERVER_VARS
<br />$HTTP_SESSION_VARS, $PATH_INFO, $HTTPS
<br />$HTTP_RAW_POST_DATA, $HTTP_X_FORWARDED_FOR
</p>

<p>
For others variables, you'll need to add '<tt>global $varname;</tt>' explicitly in your code
</p>

</div>



<div class="page">
<a name="skinvar-parsedinclude"></a>
<h1>Skin/Templatevar: parsedinclude</h1>

<p>
Includes a file into the output. The contents of the file is parsed by the Nucleus skin/template parser, so you can use skin/templatevars. (see <a href="#skinvar-phpinclude">phpinclude</a> and <a href="#skinvar-include">include</a> for other include options)
</p>

<h2>Arguments</h2>
<ul>
	<li><strong>filename</strong>: the name of the file to be included (either relative to the position of index.php, or absolute)</li>
</ul>

<h2>Notes</h2>
<ul>
	<li>This tag is affected by the <a href="#parser-properties">parser settings <code>IncludeMode</code> and <code>IncludePrefix</code></a></li>
	<li>From inside the included file, you can call <code>&lt;%parsedinclude(filename)%&gt;</code> again. To avoid endless loops, the maximum depth level you can go is 3.</li>
</ul>


<h2>Skintypes</h2>

<p>
all
</p>

<h2>Examples</h2>

<pre>
&lt;%parsedinclude(filename.txt)%&gt;
&lt;%parsedinclude(/home/user/myself/filename.txt)%&gt;
</pre>

</div>






<div class="page">
<a name="skinvar-plugin"></a>
<h1>Skin/Templatevar: plugin</h1>

<p>
Calls a plugin
</p>

<h2>Arguments</h2>
<ul>
	<li>
		<p>Required</p>
		<table><tr>
			<th>Name</th>
			<th>Contents</th>
		</tr><tr>
			<td>PlugName</td>
			<td>Name of the plugin that should be called. <strong>This name is case sensitive!</strong></td>
		</tr></table>
	</li>
	<li><p>Extra parameters can be added, depending on the plugin</p></li>
</ul>

<h2>Notes</h2>
<ul>
	<li>When a plugin name does not conflict with existing variables, it can be called directly using <code>&lt;%PluginName(parameters)%&gt;</code></li>
</ul>

<h2>Skintypes</h2>

<p>
all
</p>

<h2>Examples</h2>

<pre>
&lt;%plugin(Calendar)%&gt;
&lt;%plugin(LastComments,myweblog)%&gt;
&lt;%LastComments(myweblog)%&gt;
</pre>

</div>




<div class="page">
<a name="skinvar-loginform"></a>
<h1>Skinvar: loginform</h1>

<p>Adds a loginform, or shows a "You are karma (Log out)" message</p>

<h2>Arguments</h2>
<p>
	None
</p>

<h2>Skintypes</h2>

<p>all</p>

<h2>Examples</h2>

<pre><code>&lt;%loginform%&gt;</code></pre>

</div>




<div class="page">
<a name="skinvar-commentform"></a>
<h1>Skinvar: commentform</h1>

<p>
Adds a commentform to an item page.
</p>

<h2>Arguments</h2>
<p>
	Optional:
	<ul>
		<li><strong><em>destinationurl</em></strong>: sets the URL to where Nucleus needs to redirect after adding the comment (by default, Nucleus redirects to the item detail page for the item)</li>
	</ul>
</p>

<h2>Skintypes</h2>

<p>
item
</p>

<h2>Examples</h2>

<pre>
&lt;%commentform%&gt;
&lt;%commentform(http://host/thanks.html)%&gt;
</pre>

</div>



<div class="page">
<a name="skinvar-set"></a>
<h1>Skin/Templatevar: set</h1>

<p>
Sets a <a href="#parser-properties" title="A list of available parser properties">parser property</a>.
</p>

<h2>Arguments</h2>
<p>
	<ul>
		<li><strong>property</strong>: name of the property</li>
		<li><strong>value</strong>: value of the property</li>
	</ul>
</p>

<h2>Skintypes</h2>

<p>
all
</p>

<h2>Examples</h2>

<pre>
&lt;%set(IncludeMode,skindir)%&gt;
&lt;%set(IncludePrefix,somedir/)%&gt;
</pre>

</div>


<div class="page">
<a name="skinvar-skinfile"></a>
<h1>Skin/Templatevar: skinfile</h1>

<p>Used by imported skins to put a link relative to the skins-URL. Use it in conjunction with the <tt>IncludePrefix</tt> <a href="#parser-properties">parser property</a> to get the best results</p>

<h2>Arguments</h2>
<p>
	<ul>
		<li><strong>filename</strong>: filename of which you want the correct URL</li>
	</ul>
</p>

<h2>Skintypes</h2>

<p>
all
</p>

<h2>Examples</h2>

<pre>
&lt;%skinfile(mystyle.css)%&gt;
</pre>

</div>



<div class="page">
<a name="skinvar-skinname"></a>
<h1>Skin/Templatevar: skinname</h1>

<p>Inserts the name of the skin that's currently being used.</p>

<h2>Arguments</h2>
<p>
None
</p>

<h2>Skintypes</h2>

<p>
all
</p>

<h2>Examples</h2>

<pre>
&lt;%skinname%&gt;
</pre>

</div>



<div class="page">
<a name="skinvar-if"></a>
<a name="skinvar-else"></a>
<a name="skinvar-endif"></a>
<a name="skinvar-ifnot"></a>
<a name="skinvar-elseifnot"></a>
<a name="skinvar-elseif"></a>
<h1>Skinvars: if/ifnot/else/elseif/elseifnot/endif</h1>

<p>Inserts a content block only when certain conditions are fullfilled. Can be used in the item and comment fields of templates as of 3.60, as well as in Item bodies (same as item template fields).</p>

<h2>Arguments</h2>
<p>Only the <code>if</code>, <code>ifnot</code>, <code>elseif</code>, and <code>elseifnot</code> skinvars have options</p>


<ul>
	<li><strong>type</strong>: type of condition</li>
	<li><em>name</em>: name of option (optional)</li>
	<li><em>value</em>: value to be checked (optional)</li>
</ul>

<h2>Condition types</h2>

<ul>
	<li><strong>category</strong>: condition is fullfilled when a category is selected
		<ul>
			<li><strong>category</strong>: checks if any category is selected</li>
			<li><strong>category,catname,<em>CategoryName</em></strong>: checks if the current category is <em>CategoryName</em></li>
			<li><strong>category,catid,<em>CategoryId</em></strong>: checks if the current category is <em>CategoryId</em></li>
		</ul>
	</li>
	<li><strong>blogsetting</strong>: checks if the value <em>name</em> blogsetting equals <em>value</em> (the name is the column name from the nucleus_blog sql table)</li>
	<li><strong>loggedin</strong>: condition is fullfilled if visiting member is currently logged in</li>
	<li><strong>onteam</strong>: condition is fullfilled if visiting member is currently logged in &amp; member of the blog team of the current blog (or the blog given in the <em>name</em> parameter)</li>
	<li><strong>admin</strong>: condition is fullfilled if visiting member is currently logged in &amp; member with blog admin rights to the current blog (or the blog given in the <em>name</em> parameter)</li>
	<li><strong>nextitem</strong>: true if there is a more recent item available for the current weblog (item skintype)</li>
	<li><strong>previtem</strong>: true if there is an older item available for the current weblog (item skintype)</li>
	<li><strong>archivenextexists</strong>: true if there is a more recent archive available for the current weblog (archive skintype)</li>
	<li><strong>archiveprevexists</strong>: true if there is an older archive available for the current weblog (archive skintype)</li>
	<li><strong>skintype</strong>: checks if the current skin type is equal to <em>value</em> (index, search, item, archive, archivelist, ...). For special skin parts, the skin type is the name of the special skin part.</li>
	<li><strong>hasplugin</strong>: checks if the a plugin is installed, or if a plugin option has been set to a specific value
		<ul>
			<li><strong>hasplugin,<em>PluginName</em></strong>: checks if plugin is available</li>
			<li><strong>hasplugin,<em>PluginName</em>,<em>OptionName</em></strong>: checks if a plugin option is not set to 'no'</li>
			<li><strong>hasplugin,<em>PluginName</em>,<em>OptionName=value</em></strong>: checks if a plugin option is set to a specific value</li>
		</ul>
	</li>
	<li><strong><em>PluginName</em></strong>: checks if the a plugin is installed, and executes doIf() method of plugin to check condition of name/value pair. This allows plugins to do conditional checks in a skin. See documentation for your plugin to determine what conditionals it can perform and the syntax required for its use.
		<ul>
			<li><strong><em>PluginName</em>,<em>AttributeName</em></strong>: uses <em>PluginName</em> plugin to check if <em>AttributeName</em> has empty value</li>
			<li><strong><em>PluginName</em>,<em>AttributeName</em>,<em>AttributeValue</em></strong>: uses <em>PluginName</em> plugin to check if <em>AttributeName</em> is <em>AttributeValue</em></li>
		</ul>
	</li>
	<li><strong>itemcategory</strong>: checks conditions related to the category of the current item (item and comment template fields only)
		<ul>
			<li><strong>itemcategory</strong>: checks if current item has a category (always true)</li>
			<li><strong>itemcategory,catname,<em>CategoryName</em></strong>: checks if the category of the current item is <em>CategoryName</em></li>
			<li><strong>itemcategory,catid,<em>CategoryId</em></strong>: checks if the id of the item's category is <em>CategoryId</em></li>
		</ul>
	</li>
	<li><strong>itemblogsetting</strong>: checks if the value <em>name</em> blogsetting of the current item's blog equals <em>value</em> (the name is the column name from the nucleus_blog sql table) (item and comment template fields only)</li>
	<li><strong>author</strong>: checks conditions related to the author of the current item (item and comment template fields only)
		<ul>
			<li><strong>author</strong>: checks if the current visitor is the author of the item</li>
			<li><strong>author,isadmin</strong>: checks if the author of the item is an admin of the blog</li>
			<li><strong>author,name,<em>AuthorName</em></strong>: checks if the user name of the item's author is <em>AuthorName</em></li>
			<li><strong>author,isauthor</strong>: checks if the comment author is also the author of the item. (comment template fields only)</li>
			<li><strong>author,isonteam</strong>: checks if the comment author is a member of blog team of current item. (comment template fields only)</li>
		</ul>
	</li>
	
</ul>

<h2>Skintypes</h2>

<p>
all
</p>

<h2>Examples</h2>

<pre>
&lt;%if(loggedin)%&gt;
Welcome back!
&lt;%else%&gt;
Welcom guest!
&lt;%endif%&gt;
</pre>

<pre>
&lt;%if(category,catname,Off Topic)%&gt;
Welcome to the 'Off Topic' category.
&lt;%endif%&gt;
</pre>

<pre>
&lt;%ifnot(loggedin)%&gt;
Access Denied!
&lt;%elseif(admin)%&gt;
Welcome O Mighty Admin of this Blog!
&lt;%elseif(onteam)%&gt;
Welcome O Worthy Blog Team Member!
&lt;%else%&gt;
Welcome O Humble Site Member!
&lt;%endif%&gt;
</pre>

<h2>Notes</h2>

<p>If you want something to be displayed only if a condition is not fullfilled, you can use a construct like this:</p>

<pre>
&lt;%ifnot(skintype,error)%&gt;
&lt;%blogsetting(name)%&gt;
&lt;%endif%&gt;
</pre>

</div>






<div class="page">
<a name="skinvar-membermailform"></a>
<h1>Skinvar: membermailform</h1>

<p>
Shows a form through which a logged-in member can send a message to the member which details are being shown (on member detail pages)
</p>

<h2>Arguments</h2>
<p>
	Optional:
	<ul>
		<li><strong><em>rows</em></strong>: Amount of rows in the box (default = 10)</li>
		<li><strong><em>cols</em></strong>: Amount of columns in the box (default = 40)</li>
		<li><strong><em>destination url</em></strong>: URL to where Nucleus needs to redirection after sending the message</li>
	</ul>
</p>

<h2>Skintypes</h2>

<p>
member
</p>

<h2>Examples</h2>

<pre>
&lt;%membermailform%&gt;
</pre>

</div>






<div class="page">
<a name="skinvar-searchform"></a>
<h1>Skinvar: searchform</h1>

<p>
Shows a search form for the current blog.
</p>

<h2>Arguments</h2>
<p>
	Optional:
	<ul>
		<li><strong><em>blogname</em></strong>: The name of the blog for which you want a search form (short blog name)</li>
	</ul>
</p>

<h2>Skintypes</h2>

<p>
index, archive, archivelist, search, item
</p>

<h2>Examples</h2>

<pre>
&lt;%searchform%&gt;
&lt;%searchform(otherweblog)%&gt;
</pre>

</div>






<div class="page">
<a name="skinvar-nucleusbutton"></a>
<h1>Skinvar: nucleusbutton</h1>

<p>Inserts a nucleus button, with link to the <a href="http://nucleuscms.org/" class="out" onclick="window.open(this.href);return false;" title="Nucleus website (opens in new window)">Nucleus website</a>.</p>

<h2>Arguments</h2>
<p>
	Optional:
	<ul>
		<li><strong><em>imgurl</em></strong>: URL of the image (if you don't want the default)</li>
		<li><strong><em>imgwidth</em></strong>: width of the image (in pixels)</li>
		<li><strong><em>imgheight</em></strong>: height of the image (in pixels)</li>
	</ul>
</p>

<h2>Notes</h2>
<ul>
	<li>This tag is affected by the <a href="#parser-properties">parser settings <code>IncludeMode</code> and <code>IncludePrefix</code></a></li>
</ul>

<h2>Skintypes</h2>

<p>
all
</p>

<h2>Examples</h2>

<pre>
&lt;%nucleusbutton%&gt;
&lt;%nucleusbutton(nucleus/nucleus.gif,46,43)%&gt;
</pre>

</div>




<div class="page">
<a name="skinvar-self"></a>
<h1>Skinvar: self</h1>

<p>
Inserts the filename of the page currently being displayed (index.php or whatever you changed it to)
</p>

<h2>Arguments</h2>
<p>None</p>

<h2>Skintypes</h2>

<p>
all
</p>

<h2>Examples</h2>

<pre>
&lt;%self%&gt;
</pre>

</div>


<div class="page">
<a name="skinvar-addlink"></a>
<h1>Skinvar: addlink</h1>

<p>
Inserts a URL to the new item bookmarklet form. Only shown for members who have rights on the current blog.
</p>

<h2>Arguments</h2>
<p>None</p>

<h2>Skintypes</h2>

<p>
all
</p>

<h2>Examples</h2>

<pre>
&lt;dd&gt;&lt;a href="&lt;%addlink%&gt;" onclick="&lt;%addpopupcode%&gt;" title="Add an item to your blog"&gt;Add an item&lt;/a&gt;&lt;/dd&gt;
</pre>

</div>

<div class="page">
<a name="skinvar-addpopupcode"></a>
<h1>Skinvar: addpopupcode</h1>

<p>
Inserts javascript code to open a bookmarklet in an popup window. Use with <code>&lt;%addlink%&gt;</code>
</p>

<h2>Arguments</h2>
<p>None</p>

<h2>Skintypes</h2>

<p>
all
</p>

<h2>Examples</h2>

<pre>
&lt;dd&gt;&lt;a href="&lt;%addlink%&gt;" onclick="&lt;%addpopupcode%&gt;" title="Add an item to your blog"&gt;Add an item&lt;/a&gt;&lt;/dd&gt;
</pre>

</div>


<div class="page">
<a name="skinvar-sticky"></a>
<h1>Skinvar: sticky</h1>

<p>
Inserts the indicated item into the skin.
</p>

<h2>Arguments</h2>
<p>
	Required:
	<ul>
		<li><strong>itemid</strong>: id of the item to show</li>
		<li><strong>template</strong>: name of the template to use</li>
	</ul>
</p>

<h2>Skintypes</h2>

<p>
all
</p>

<h2>Examples</h2>

<pre>
&lt;%sticky(11,default/index)%&gt;
</pre>

</div>



<div class="page">
<a name="templatevars-overview"></a>
<h1>Template variables: Overview</h1>

<h2>What?</h2>

<p>Template variables largely work in exact the same way as skin variables, with the only difference that they are being used inside templates. The variables are called using <code>&lt;%<i>varname</i>%&gt;</code>, and include some text depending on the variable function. Some variables also have extra optional parameters.</p>

<h2>Available variables</h2>

<p>
These template variables be used in the following template-parts: <tt>item header, item body, item footer, date header, date footer, morelink, editlink</tt> (The variables <tt>image</tt>, <tt>popup</tt> and <tt>media</tt> can also be used inside weblog items.)
</p>

<ul>
	<li><a href="#templatevars-basic">Basic variables...</a> (title, body, ...)</li>
	<li><a href="#templatevars-advanced">Advanced variables...</a> (include, plugin, ...)</li>
</ul>

<p>Comments-related template-parts (<tt>comments header, comments body, comments footer, one comment, two comments, comments read more, no comments, too much comments</tt>) have a different set of available variables:</p>

<ul>
	<li><a href="#templatevars-comments">Comments-related variables...</a></li>
</ul>


</div>



<div class="page">
<a name="templatevars-basic"></a>
<h1>Template variables: Basic variables</h1>

<p>All these variables concern the item that's currently being parsed.</p>

<table><tr>
	<th>Name</th>
	<th>Description</th>
</tr><tr>
	<td>title</td>
	<td>item title</td>
</tr><tr>
	<td>body</td>
	<td>body text</td>
</tr><tr>
	<td>more</td>
	<td>extended text</td>
</tr><tr>
	<td>category</td>
	<td>name of the category</td>
</tr><tr>
	<td>categorylink</td>
	<td>raw link to the category</td>
</tr><tr>
	<td><a href="#templatevar-karma">karma</a></td>
	<td>karma score</td>
</tr><tr>
	<td>authorlink</td>
	<td>raw link to the author</td>
</tr><tr>
	<td>itemlink</td>
	<td>raw permanent link for the item</td>
</tr><tr>
	<td><a href="#templatevar-author">author</a></td>
	<td>name of the author</td>
</tr><tr>
	<td><a href="#templatevar-smartbody">smartbody</a></td>
	<td>either the body text or the extended text</td>
</tr><tr>
	<td><a href="#templatevar-morelink">morelink</a></td>
	<td>'read more'-link</td>
</tr><tr>
	<td><a href="#templatevar-date">date</a></td>
	<td>Formatted date</td>
</tr><tr>
	<td><a href="#templatevar-time">time</a></td>
	<td>Formatted time</td>
</tr><tr>
	<td>daylink</td>
	<td>raw link to the daily archive</td>
</tr><tr>
	<td><a href="#templatevar-comments">comments</a></td>
	<td>comments block or commentcount</td>
</tr><tr>
	<td>itemid</td>
	<td>ID of the item</td>
</tr><tr>
	<td>blogurl</td>
	<td>URL of the blog</td>
</tr></table>

<p><a href="#templatevars-overview">Template variables overview...</a></p>


</div>



<div class="page">
<a name="templatevars-advanced"></a>
<h1>Template variables: Advanced variables</h1>


<table><tr>
	<th>Name</th>
	<th>Description</th>
</tr><tr>
	<td>authorid</td>
	<td>ID of the current items author</td>
</tr><tr>
	<td>blogid</td>
	<td>ID of the blog</td>
</tr><tr>
	<td>catid</td>
	<td>ID of the category for the current item</td>
</tr><tr>
	<td>query</td>
	<td>search query (if there is one)</td>
</tr><tr>
	<td><a href="#templatevar-syndicate_title">syndicate_title</a></td>
	<td>Syndicated title</td>
</tr><tr>
	<td><a href="#templatevar-syndicate_description">syndicate_description</a></td>
	<td>Syndicated body text</td>
</tr><tr>
	<td>karmaposlink</td>
	<td>raw vote link</td>
</tr><tr>
	<td>karmaneglink</td>
	<td>raw vote link</td>
</tr><tr>
	<td>new</td>
	<td>'New Item!'-text</td>
</tr><tr>
	<td><a href="#skinvar-include">include</a></td>
	<td>includes a file, whithout parsing</td>
</tr><tr>
	<td><a href="#skinvar-parsedinclude">parsedinclude</a></td>
	<td>includes a file, parsing it</td>
</tr><tr>
	<td><a href="#skinvar-phpinclude">phpinclude</a></td>
	<td>includes a file, parsing by PHP</td>
</tr><tr>
	<td><a href="#skinvar-if">if-ifnot-else-elseif-elseifnot-endif</a></td>
	<td>performs condition statements in templates (3.60)</td>
</tr><tr>
	<td><a href="#skinvar-plugin">plugin</a></td>
	<td>executes a plugin</td>
</tr><tr>
	<td><a href="#templatevar-edit">edit</a></td>
	<td>inserts an 'edit this item' link</td>
</tr><tr>
	<td><a href="#templatevar-editlink">editlink</a></td>
	<td>raw 'edit item' link (links to bookmarklet)</td>
</tr><tr>
	<td><a href="#templatevar-editpopupcode">editpopupcode</a></td>
	<td>javascript code to open a popup window for editlink</td>
</tr><tr>
	<td><a href="#skinvar-skinfile">skinfile</a></td>
	<td>includes the correct URL for a file belonging to an imported skin</td>
</tr><tr>
	<td><a href="#skinvar-set">set</a></td>
	<td>sets a parser property</td>
</tr><tr>
	<td><a href="#templatevar-image">image</a></td>
	<td>inline image from media library</td>
</tr><tr>
	<td><a href="#templatevar-popup">popup</a></td>
	<td>popup image from media dir</td>
</tr><tr>
	<td><a href="#templatevar-media">media</a></td>
	<td>other media object from media dir</td>
</tr><tr>
	<td>relevance</td>
	<td>Includes the 'search hit relevance' in templates that display search results</td>
</tr></table>

<p><a href="#templatevars-overview">Template variables overview...</a></p>

</div>




<div class="page">
<a name="templatevars-comments"></a>
<h1>Template variables: Comments</h1>


<table><tr>
	<th>Name</th>
	<th>Description</th>
</tr><tr>
	<td>body</td>
	<td>comment body</td>
</tr><tr>
	<td>user</td>
	<td>user name</td>
</tr><tr>
	<td>userid</td>
	<td>users URL or e-mail address</td>
</tr><tr>
	<td>userlink</td>
	<td>a smart link to either the e-mail or URL for non members, or the member detail page for members. Note: this link already includes the &lt;a href="..."&gt; and &lt;/a&gt; tags ! (when no valid URL or e-mail is available, only the name of the member will be shown)</td>
</tr><tr>
	<td>userlinkraw</td>
	<td>same as above, but without the &lt;a href.., empty when no valid URL or e-mail available</td>
</tr><tr>
	<td>useremail</td>
	<td>the e-mail address of the user, empty if the e-mail address was not provided by the user</td>
</tr><tr>
	<td>userwebsite</td>
	<td>the URL of the users website, empty if the URL was not provided by the user</td>
</tr><tr>
	<td>userwebsitelink</td>
	<td>a smart link to URL for non members, or the member detail page for members. Note: this link already includes the &lt;a href="..."&gt; and &lt;/a&gt; tags ! (when no valid URL, only the name of the member will be shown)</td>
</tr><tr>
	<td>memberid</td>
	<td>ID of the member (0 for non-members)</td>
</tr><tr>
	<td>commentcount</td>
	<td>total amount of comments for the item</td>
</tr><tr>
	<td><a href="#templatecommentwords" title="commentword()">commentword</a></td>
	<td>1 'comment', 2 'comments'</td>
</tr><tr>
	<td><a href="#templatevar-date" title="date([format])">date</a></td>
	<td>date on which comment was added</td>
</tr><tr>
	<td><a href="#templatevar-time" title="time([format])">time</a></td>
	<td>time at which comment was added</td>
</tr><tr>
	<td>host</td>
	<td>host from where comment was added</td>
</tr><tr>
	<td>ip</td>
	<td>IP-address from where comment was added</td>
</tr><tr>
	<td>commentid</td>
	<td>ID of the current comment</td>
</tr><tr>
	<td>itemid</td>
	<td>ID of the current item</td>
</tr><tr>
	<td>itemlink</td>
	<td>link to the detailed item page</td>
</tr><tr>
	<td><a href="#templateitemtitle" title="itemtitle([maxlength])">itemtitle</a></td>
	<td>Title of the current item</td>
</tr><tr>
	<td>blogid</td>
	<td>ID of the weblog</td>
</tr><tr>
	<td>blogurl</td>
	<td>URL of the weblog</td>
</tr><tr>
	<td><a href="#templatememberextra" title="authtext()">authtext</a></td>
	<td>the extra text</a> for members, empty for non members</td>
</tr><tr>
	<td>short</td>
	<td>a cut off version of the body, which truncates after the first line break. <a href="#templatecommentcontinued">A link is added</a> at the end according to the template</td>
</tr><tr>
	<td>excerpt</td>
	<td>the body of the comment, cut at 60 characters and appended with '...'</td>
</tr><tr>
	<td>timestamp</td>
	<td>time at which comment was added</td>
</tr><tr>
	<td><a href="#skinvar-if">if-ifnot-else-elseif-elseifnot-endif</a></td>
	<td>performs condition statements in templates (3.60)</td>
</tr><tr>
	<td><a href="#skinvar-include" title="include(filename)">include</a></td>
	<td>includes a file, whithout parsing</td>
</tr><tr>
	<td><a href="#skinvar-parsedinclude" title="parsedinclude(filename)">parsedinclude</a></td>
	<td>includes a file, parsing it</td>
</tr><tr>
	<td><a href="#skinvar-phpinclude" title="phpinclude(filename)">phpinclude</a></td>
	<td>includes a file, parsing by PHP</td>
</tr><tr>
	<td><a href="#skinvar-plugin" title="plugin(name,[options...])">plugin</a></td>
	<td>executes a plugin</td>
</tr><tr>
	<td><a href="#skinvar-skinfile" title="skinfile(filename)">skinfile</a></td>
	<td>includes the correct URL for a file belonging to an imported skin</td>
</tr><tr>
	<td><a href="#skinvar-set" title="set(property,value)">set</a></td>
	<td>sets a parser property</td>
</tr></table>



<p><a href="#templatevars-overview">Template variables overview...</a></p>

</div>



<div class="page">
<a name="templatevar-karma"></a>
<h1>Templatevar: karma</h1>

<p>Inserts karma votes data. Karma votes are a method to vote the 'karma' of an item. With a single click, the visitor can vote either positive or negative. The total of all these votes gives an idea of how much an item is liked by the visitors</p>

<h2>Arguments</h2>


<ul>Optional:
	<ul>
		<li><strong><em>what</em></strong>: Choose a type of information to be displayed:
			<ul>
				<li><strong>totalscore</strong>: the total karma vote score (=amount of positive votes minus the amount of negative votes) <em>(default)</em></li>
				<li><strong>pos</strong>: total number of positive votes</li>
				<li><strong>neg</strong>: total number of negative votes</li>
				<li><strong>votes</strong>: total number of votes</li>
				<li><strong>posp</strong>: percentage of votes that is positive</li>
				<li><strong>negp</strong>: percentage of votes that is negative</li>
			</ul>
		</li>
	</ul>
</ul>

<h2>Examples</h2>
<pre><code>&lt;%karma(posp)%&gt; out of &lt;%karma(votes)%&gt; were positive</code></pre>


</div>



<div class="page">
<a name="templateitemtitle"></a>
<h1>Templatevar: templateitemtitle</h1>

<p>On comments-releated templateparts, inserts the title of the associated item.</p>

<h2>Arguments</h2>

<ul>Optional:
	<ul>
		<li><strong><em>maxlength</em></strong>: When provided, makes the itemtitle behave like the <a href="#templatevar-syndicate_title">syndicate_title templatevar</a>.
		</li>
	</ul>
</ul>

</div>






<div class="page">
<a name="templatevar-author"></a>
<h1>Templatevar: author</h1>

<p>Inserts the name of the author</p>

<h2>Arguments</h2>
<ul>Optional:
	<ul>
		<li><strong><em>what</em></strong>: Choose a type of information to be displayed:
			<ul>
				<li><strong>name</strong>: display name <em>(default)</em></li>
				<li><strong>realname</strong>: the real name of the author instead of the display name</li>
				<li><strong>id</strong>: Nucleus membet ID</li>
				<li><strong>url</strong>: URL of members website</li>
				<li><strong>email</strong>: email address of member (use of this one should be avoided)</li>
			</ul>
		</li>
	</ul>
</ul>

<h2>Examples</h2>

<pre><code>&lt;%author%&gt;
&lt;%author(realname)%&gt;
&lt;a href="&lt;%author(url)%&gt;"&gt;&lt;%author%&gt;&lt;/a&gt;</code></pre>

</div>




<div class="page">
<a name="templatevar-smartbody"></a>
<h1>Templatevar: smartbody</h1>

<p>
Examines the current item and then decides to show either the body text or the expanded text.
</p>

<p>When the extended part is empty, the body part is chosen. Otherwise the extended part is shown.</p>

<table style="text-align: center;"><tr>
	<th>Part</th><th colspan="2">Empty?</th>
</tr><tr>
	<td>Body</td><td>No</td><td>No</td>
</tr><tr>
	<td>Extended</td><td>Yes</td><td>No</td>
</tr><tr>
	<th>smartbody=</th><th>body part</th><th>extended part</th>
</tr></table>

<h2>Example use</h2>

<p>The body text could be interpreted as your full text, and the extended part could be interpreted as an 'introduction' or 'exerpt', which you want to show on the front page.</p>
<p>In the template used on the front page, you would use <tt>&lt;%smartbody%&gt;</tt> to insert an excerpt (if there is one), or the full text (if no excerpt). In the template for detailed items, <tt>&lt;%body%&gt;</tt> can then be used instead of the usual <tt>&lt;%body%&gt;</tt> + <tt>&lt;%more%&gt;</tt>, since <tt>&lt;%body%&gt;</tt> will contain the full item anyway.</p>




</div>


<div class="page">
<a name="templatevar-morelink"></a>
<h1>Templatevar: morelink</h1>

<p>
Inserts a link to the detail page for the item, as defined in the template (<a href="#templatemorelink">link to extended entry</a>). This is empty when there is no extended part.
</p>

<p>Note that the contents of the 'link to extended entry' templatepart is also parsed and can thus also contain <a href="#templatevars-overview">templatevariables</a>.</p>
</div>


<div class="page">
<a name="templatevar-date"></a>
<h1>Templatevar: date</h1>

<p>
Inserts a date using the <a href="#templatedatetime">date format specified in the template</a>. Optionally, a custom date format can be given as a parameter.
</p>

<h2>Arguments</h2>
<ul>Optional
	<ul>
		<li><strong><i>format</i></strong>: format to be used to format the date</li>
	</ul>
</ul>

<h2>Specials</h2>

<p>Four special parameters are possible:</p>
<ol>
 <li><code>rfc822</code>: RFC822 date in local time</li>
 <li><code>rfc822GMT</code>: RFC date in GMT time</li>
 <li><code>iso8601</code>: ISO-8601 date (<a href="http://www.w3.org/TR/NOTE-datetime">W3C Date and Time Format</a> profile). Example: 2002-10-02T10:00:00-05:00</li>
 <li><code>utc</code>: Same as iso8601, but the date is expressed in UTC, using a "Z" for the timezone indicator.</li>
</ol>

<h2>Examples</h2>
<pre>
&lt;%date%&gt;
&lt;%date(%x)%&gt;
&lt;%date(rfc822)%&gt;
&lt;%date(rfc822GMT)%&gt;
</pre>


</div>

<div class="page">
<a name="templatevar-time"></a>
<h1>Templatevar: time</h1>

<p>
Inserts a time using the <a href="#templatedatetime">time format specified in the template</a>. Optionally, a custom time format can be given as a parameter.
</p>

<h2>Arguments</h2>
<ul>Optional
	<ul>
		<li><strong><i>format</i></strong>: format to be used to format the time</li>
	</ul>
</ul>

<h2>Examples</h2>
<pre>
&lt;%time%&gt;
&lt;%time(%X)%&gt;
</pre>

</div>


<div class="page">
<a name="templatevar-comments"></a>
<h1>Templatevar: comments</h1>

<p>
Inserts a comments 'block'. <a href="#templatecomments">More information about the structure of this block</a>.
</p>

<h2>Arguments</h2>
<ul><p>Optional:</p>
	<table><tr>
		<th>Name</th>
		<th>Contents</th>
	</tr><tr>
		<td>MaxToShow</td>
		<td>Amount of comments to show (when set, this overrides the <a href="#blogmaxcomments">max. comments blogsetting</a>)</td>
	</tr></table>
</ul>

<h2>Examples</h2>

<pre>
&lt;%comments%&gt;
&lt;%comments(5)%&gt;
</pre>

</div>


<div class="page">
<a name="templatevar-syndicate_title"></a>
<h1>Templatevar: syndicate_title</h1>

<p>
Inserts the title of the item, with HTML tags-stripped off, and shortened to 100 characters. When the text needs to be shortened, "..." is added at the end of the text.
</p>

<p>
This variable was originally intended for use in the XML-RSS skin that comes with Nucleus, but can also be of use in other situations.
</p>

<h2>Arguments</h2>
<ul>
	<li>
		<p>Optional:</p>
		<table><tr>
			<th>Name</th>
			<th>Contents</th>
		</tr><tr>
			<td>MaxChars</td>
			<td>Maximum amount of characters to keep (defaults to 100)</td>
		</tr></table>
	</li>
</ul>

<h2>Examples</h2>

<pre>
&lt;%syndicate_title%&gt;
&lt;%syndicate_title(25)%&gt;
</pre>

</div>

<div class="page">
<a name="templatevar-syndicate_description"></a>
<h1>Templatevar: syndicate_description</h1>

<p>
Inserts the body of the item, with HTML tags-stripped off, and shortened to 250 characters. When the text needs to be shortened, "..." is added at the end of the text.
</p>

<p>
This variable was originally intended for use in the XML-RSS skin that comes with Nucleus, but can also be of use in other situations.
</p>

<h2>Arguments</h2>
<ul>
	<li>
		<p>Optional:</p>
		<table><tr>
			<th>Name</th>
			<th>Contents</th>
		</tr><tr>
			<td>MaxChars</td>
			<td>Maximum amount of characters to keep (defaults to 250)</td>
		</tr></table>
	</li>
</ul>

<h2>Examples</h2>

<pre>
&lt;%syndicate_description%&gt;
&lt;%syndicate_description(25)%&gt;
</pre>

</div>


<div class="page">
<a name="templatevar-image"></a>
<h1>Templatevar: image</h1>

<p>Inserts an inline image into an item body or template.</p>

<p>In normal use, the image-templatevar is generated automatically when adding images through the media library. You can call it from within templates too, though. Note that in this last case, the image will come out of the media dir of the current item's author.</p>

<h2>Arguments</h2>
<ul>
	<li>
		<p>Required:</p>
		<table><tr>
			<th>Name</th>
			<th>Contents</th>
		</tr><tr>
			<td>filename</td>
			<td>Name of the image file (file gets)</td>
		</tr><tr>
			<td>width</td>
			<td>Width of the image (pixels or percentage)</td>
		</tr><tr>
			<td>height</td>
			<td>Height of the image</td>
		</tr><tr>
			<td>text</td>
			<td>alt-text for the image</td>
		</tr></table>
	</li>
	<li><strong>Note:</strong> for the image, popup and media tags, the parameters must be separated by the '|' character, <em>not</em> by a comma!</li>
</ul>

<h2>Examples</h2>

<pre>
&lt;%image(myphoto.jpg|100|200|this is me)%&gt;
&lt;%image(myphoto.jpg|50%|50%|this is me, but smaller)%&gt;
</pre>

</div>



<div class="page">
<a name="templatevar-popup"></a>
<h1>Templatevar: popup</h1>

<p>Inserts a popup image into an item body or template.</p>

<p>In normal use, the popup-templatevar is generated automatically when adding images through the media library. You can call it from within templates too, though. Note that in this last case, the image will come out of the media dir of the current item's author.</p>

<h2>Arguments</h2>
<ul>
	<li>
		<p>Required:</p>
		<table><tr>
			<th>Name</th>
			<th>Contents</th>
		</tr><tr>
			<td>filename</td>
			<td>Name of the image file (file gets)</td>
		</tr><tr>
			<td>width</td>
			<td>Width of the image (pixels or percentage)</td>
		</tr><tr>
			<td>height</td>
			<td>Height of the image</td>
		</tr><tr>
			<td>text</td>
			<td>alt-text for the image</td>
		</tr></table>
	</li>
	<li><strong>Note:</strong> for the image, popup and media tags, the parameters must be separated by the '|' character, <em>not</em> by a comma!</li>
</ul>

<h2>Examples</h2>

<pre>
&lt;%popup(myphoto.jpg|100|200|this is me)%&gt;
&lt;%popup(myphoto.jpg|50%|50%|this is me, but smaller)%&gt;
</pre>

</div>



<div class="page">
<a name="templatevar-media"></a>
<h1>Templatevar: media</h1>

<p>Inserts a media object into an item body or template.</p>

<p>In normal use, the media-templatevar is generated automatically when adding images through the media library. You can call it from within templates too, though. Note that in this last case, the object will come out of the media dir of the current item's author.</p>

<h2>Arguments</h2>
<ul>
	<li>
		<p>Required:</p>
		<table><tr>
			<th>Name</th>
			<th>Contents</th>
		</tr><tr>
			<td>filename</td>
			<td>Name of the image file (file gets)</td>
		</tr><tr>
			<td>text</td>
			<td>descriptive text for the media object</td>
		</tr></table>
	</li>
	<li><strong>Note:</strong> for the image, popup and media tags, the parameters must be separated by the '|' character, <em>not</em> by a comma!</li>
</ul>

<h2>Examples</h2>

<pre><code>&lt;%media(mysong.mp3|listen to my new song)%&gt;</code></pre>

</div>


<div class="page">
<a name="templatevar-edit"></a>
<h1>Templatevar: edit</h1>

<p>
From within your template, you can add an 'edit item' link by using this template variable. By default, it will link to a popup-bookmarklet-window, but that behaviour can be changed through the <a href="#templateeditlink">editlink template</a>.
</p>

<p><strong>Note:</strong> only logged in members that are allowed to edit the item will see this link. In other cases, the edit-templatevar does nothing at all.</p>

<h2>Example</h2>
<p>An example for the item body template</p>
<pre><code>&lt;h1&gt;&lt;%title%&gt;&lt;/h1&gt;
&lt;p&gt;&lt;%body%&gt; &lt;%morelink%&gt;&lt;/p&gt;
&lt;div class="metadata"&gt;
	&lt;%edit%&gt; &lt;%comments%&gt;
&lt;/div&gt;</code></pre>

<h2>Results in</h2>

<div class="example">
<h4 style="margin:2px;">Title</h4>
<p style="margin:2px;">This is an item</p>
<div style="margin:2px;"><a href="#templatevar-edit">edit</a> - <a href="#templatevar-edit">5 comments</a></div>
</div>

</div>


<div class="page">
<a name="templatevar-editlink"></a>
<h1>Templatevar: editlink</h1>

<p>
Insert a link to the 'edit item' bookmarklet. This can be used in the <a href="#templateeditlink">editlink template</a> for simplicity.
</p>

<h2>Example</h2>

<p>The <a href="#templateeditlink">'edit link'-template</a> could look like this:</p>
<pre>
&lt;a href="&lt;%editlink%&gt;"
   onclick="&lt;%editpopupcode%&gt;"&gt;edit&lt;/a&gt; -
</pre>

</div>


<div class="page">
<a name="templatevar-editpopupcode"></a>
<h1>Templatevar: editpopupcode</h1>

<p>
To open a popup window for the 'edit link' window, you'll need to add some javascript code to your link. To avoid having to enter this code in the 'edit link'-template, you can insert it using the editpopupcode-templatevar.
</p>

<h2>Example</h2>
<p>See the example for the <a href="#templatevar-editlink">editlink templatevar</a></p>
</div>



<div class="page">
<a name="plugins"></a>
<h1>Plugins</h1>
<p>
Nucleus allows you to install custom plugins, adding extra functionality. Plugins can do different things:
</p>
<ol>
	<li>Act as a skin variable</li>
	<li>Act as a template variable</li>
	<li>Hook into events generated by Nucleus. The 'move up' and 'move down' links in 'manage plugins' screen can be used to define the order in which plugins will be called when such an event occurs. The first plugin in the list will be called first, the last one will be called last.</li>
	<li>Act as actors when called through <tt>action.php</tt></li>
</ol>
<p>
Note that the responsibility for plugins is entirely with the plugin author. He should make sure that everything works fine.
</p>
<a name="getplugins"></a>
<p>
There are two main repositories where you can find plugins for Nucleus CMS:
</p>
<ul>
	<li><a href="http://wiki.nucleuscms.org/plugin" title="Plugin Wiki">English</a></li>
	<li><a href="http://japan.nucleuscms.org/wiki/plugins" title="Japanese Plugin Wiki">Japanese</a></li>
</ul>
<p>
Neither or these repositories is entirely complete. You will find some plugins in one, but not in the other, and vice versa. 
Do not be scared off of one or the other on account of language, as there are a few free translation services on the Internet that 
will help you get by.
</p>
Another resource that will help you while working with plugins is the search function at the 
<a href="http://forum.nucleuscms.org/" title="Support Forum">support forum</a>. You will even find some 
smaller plugins on the forum that never made it to the wiki.
<p>
</p>
</div>

<div class="page">
<a name="parser-properties"></a>
<a name="includemode"></a>
<a name="includeprefix"></a>
<h1>Parser Properties</h1>

<p>The available parser options are described below.</p>

<table>
 <caption>Parser properties</caption>
 <tr>
 	<th>Option Name</th>
	<th>Values</th>
 </tr><tr>
 	<td>IncludeMode</td>
	<td>
		<ul>
			<li><strong>normal</strong>: normal behaviour; included files are taken relative to the directory/url of the .php file generating the page.</li>
			<li><strong>skindir</strong>: included files are taken relative to the skindir/skinurl</li>
		</ul>
		<p>This property affects the following skinvars: <a href="#skinvar-include">include</a>, <a href="#skinvar-phpinclude">phpinclude</a>, <a href="#skinvar-parsedinclude">parsedinclude</a>, <a href="#skinvar-nucleusbutton">nucleusbutton</a></p>
	</td>
 </tr><tr>
 	<td>IncludePrefix</td>
 	<td>
		<p>This property is a prefix that get's added in front of each filename you want to include. For example, if the prefix is <tt>base/</tt> and you want to include <tt>somefile.txt</tt>, you'll end up including <tt>base/somefile.txt</tt></p>
		<p>This property is intended to be used in conjunction with the IncludeMode property. This way, a skin imported to <tt><em>skindir/</em>somename/</tt> can set <tt>IncludeMode</tt> to <tt>skindir</tt> and <tt>IncludePrefix</tt> to <tt>somename/</tt></p>
		<p>This property affects the following skinvars: <a href="#skinvar-include">include</a>, <a href="#skinvar-phpinclude">phpinclude</a>, <a href="#skinvar-parsedinclude">parsedinclude</a>, <a href="#skinvar-nucleusbutton">nucleusbutton</a></p>
	</td>
  </tr>
</table>

<p>The <tt>IncludePrefix</tt> and <tt>IncludeMode</tt> properties can be set globally for a skin in the general settings of a skin. Also note that from the moment a property is set, it applies to all parsed data, thus also for templates.</p>

</div>

</body>
</html>
